build-skills

You can automate skill implementation by reading design artifacts from the studio changes workflow, specifically studio/changes/status.json and skill-map.md. The build process identifies in-scope skills and uses the skill-creator to flesh out working draft skeletons for testing.

Generating skill skeletons requires a studio directory containing status.json in studio/changes, a skill-map.md file to determine in-scope skills, a target_dir for implementations, and access to the internal skill-creator capability.

The skill build workflow supports both create and modify iterations. It reads status.json to determine the iteration type and uses skill-creator to flesh out skeletons into working drafts suitable for both new and modified skill implementations.

Scaffolding working drafts from status.json involves confirming the build stage, letting the system identify in-scope skills from the file and skill-map.md, then using skill-creator to generate initial implementations in the target directory for testing with real inputs.

No, this automated build process requires a studio directory structure with status.json in studio/changes and a skill-map.md file. Without these design artifacts, the system cannot determine in-scope skills or generate initial implementations.

The best way to integrate validation is to follow the build workflow after skill-creator generates initial implementations. The system guides users through the build process and integration with validation steps to ensure the working drafts function correctly with real inputs.