spec-generate

To generate plugin spec files, you read existing planning artifacts like skill-map.md and status.json, then use template rendering to automatically emit brief.md, plugin.json.draft, and SKILL.md skeletons into your target plugin workspace.

Trait-driven build scaffolding detects specific traits in your skill map to conditionally generate runtime workspace files, approval-gate sections for human-in-the-loop gating, and pipeline orchestration commands alongside standard spec files.

You scaffold build-ready skills deterministically by processing existing skill maps and status files to output SKILL.md and commands/*.md files, bypassing interactive brainstorming to directly produce implementation structure for the build stage.

Yes, you can use markdown and yaml planning files as input to automate command generation, reading studio workspace artifacts to render and write user-invocable command files into the target plugin directory.

Plugin spec generation outputs include brief.md, plugin.json.draft, skills/*/SKILL.md, commands/*.md, and an updated status.json file reflecting building-ready draft skills within your studio changes directory.