build-skills

To generate skill implementations from a spec, this tool builds initial first-draft code in a target plugin directory after spec generation and skeleton creation. It reads studio change workspaces and applies internal skill-creator capabilities to scaffold working drafts.

Plugin scaffolding produces iteration-ready code with substance that is testable but not production-polished. It creates initial skill implementations designed for follow-up refinement via skill-creator and later validation.

Workspace build control uses status.json to define scope. For create iterations, it builds every skill listed; for modify iterations, it rebuilds only in-scope skills to avoid unintended changes to existing implementations.

Yes, you need spec generation and skeleton creation beforehand. The building phase requires a pre-check to confirm these stages are complete before invoking the internal skill-creator per skill.

Status tracking updates status.json to reflect draft, building, or built outcomes. It monitors each skill during generation and updates SKILL.md files in place only when modifications are needed.

No, the generated first-draft code is explicitly not production-polished. It produces scaffolding with substance that is testable and designed for follow-up refinement via skill-creator and later validation.