[clabonte]

Closes #172.

Bug. The /generate skill ran specfuse authoring generate --group "<group>" <project>-project.json. The launcher passes everything after generate to the jar unchanged, so the jar got no subcommand. I reproduced this against the 0.19.0 jar:

$ java -jar specfuse-generator-0.19.0.jar --group Backend hello-orders-project.json
Unknown option: --group
OpenAPI DDD Code Generator
Usage: java -jar openapi-ddd.jar <command> [options]

Nothing was generated.

Changes

• skills/generate/SKILL.md
  • Runs specfuse authoring generate generate --progress --group … and explains why generate appears twice.
  • Removed the hardcoded C#, Flutter and C#-workers steps. The skill now reads the groups from the project file, selects the ones the user named or asks which to run, and treats all as opt-in only.
  • Before a regen, checks that out-of-repo destinations (for example ../Backend/) have no uncommitted changes, because cleanGenerated deletes before it rewrites.
  • Bundles OpenAPI, and AsyncAPI when the project has it, then runs one invocation per group.
  • Adds the Dart build_runner post-step.
  • Keeps generate-scenario-docs.sh for the Markdown groups.
  • Reports the result per group, with exit-code meanings.
• docs/getting-started.md and docs/generator-access.md showed specfuse authoring generate <args>, which invites the same mistake. Both now show the full command and a one-line explanation.

Verified. specfuse authoring generate generate --group Domain hello-orders-project.json on a copy of examples/hello-orders exits 0 and writes 13 .cs files. The installed CLI is the released kit, which uses generator 0.18.0. There's no pytest suite. The plugin-substrate check isn't affected because no methodology paths were cited.

Note. #173 also edits getting-started.md §5, on nearby lines. Whichever PR merges second may need a trivial rebase.

🤖 Generated with Claude Code