spec-generate

To auto-generate plugin specs from planning artifacts, you run a deterministic process that transforms skill-map.md, event-storm.md, and domain-map.md into runnable workspace scaffolds. It writes SKILL.md skeletons, plugin.json.draft files, and briefs without requiring interactive input.

Scaffolding a plugin manifest and SKILL.md skeleton is best handled by parsing existing planning outputs like skill maps and domain maps. This approach generates plugin.json.draft files and per-skill command structures directly into the target plugin directory.

No interactive input is needed to generate a runnable plugin workspace. The generation process is deterministic, relying entirely on parsed planning artifacts to emit ready-for-build artifacts like studio/changes briefs and status coordinators.

Generating command scaffolds from a skill map accelerates build readiness by automating the creation of per-skill orchestration artifacts. This eliminates manual scaffolding, allowing implementation to proceed immediately using the produced studio/changes briefs.

Yes, you can use event-storm.md and domain-map.md to create studio/changes briefs. These planning documents are parsed to drive the build process, automatically producing status scaffolds and plugin manifests under the target directory.

You should not use automation for plugin specification generation if your planning artifacts like skill-map.md or domain-map.md are incomplete or missing. The process requires these inputs to deterministically write SKILL.md skeletons and command scaffolds correctly.