From studio-planner
Generate initial skill implementations in the target plugin directory after spec generation. Produces working first drafts that need iterative refinement through testing and skill-creator. Use when the user has confirmed the build stage. Works for both create and modify iterations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/studio-planner:build-skillsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build the implementation for a plugin after `spec-generate` has produced the design artifacts and initial skeletons.
Build the implementation for a plugin after spec-generate has produced the design artifacts and initial skeletons.
This stage is responsible for automatic skill construction. Users confirm entry into this stage, but they do not manually run skill-creator themselves.
Take a plugin workspace in studio/changes/{plugin}/ plus the implementation files in {target_dir}/, determine which skills need work in this iteration, and use skill-creator as an internal build capability to produce initial implementations.
This stage produces "scaffolding with substance" — skill implementations that are complete enough to test but not yet production-ready. Think of it as a working first draft:
| What the initial fill provides | What iterative refinement adds |
|---|---|
| Correct structure and flow | Edge case handling |
| Core workflow steps | Real-world tested prompts |
| Input/output contracts | Polished user-facing messages |
| Basic precondition checks | Domain-specific quality rules |
| Placeholder examples | Validated examples from actual usage |
Users should test each skill with 2-3 real scenarios and iterate with skill-creator before proceeding to validation. This is the normal and expected workflow — not a sign that build failed.
studio/ exists.studio/changes/$ARGUMENTS/status.json — required.phase is building. If not:
planning → tell the user to complete spec-generate firstapproved → tell the user the plugin is already built and validatedshipped → tell the user the active change workspace has already been promotedtarget_dir, action, and skills from status.json.studio/changes/$ARGUMENTS/skill-map.md — required.{target_dir}/skills/ exists.This stage follows these rules:
target_dir is the single source of truth for implementationSKILL.md files are updated in place when neededaction: "create"status.json.skills is in scope{target_dir}/skills/{name}/SKILL.md should be builtskill-creator to flesh out each skeletonaction: "modify"status.json.skills are in scopeFor each in-scope skill:
buildingSKILL.mdskill-map.mdSKILL.mdskill-creator as an internal build capability to:
builtdraft or set it to building-failed if the workspace schema supports itUpdate studio/changes/{plugin}/status.json as the build progresses.
Recommended progression:
draft → spec exists but build not startedbuilding → currently being processedbuilt → implementation updated successfullytested → validation passed laterKeep the plugin phase as building during this stage.
If all in-scope skills were built successfully:
phase as building/studio-quality:validate {target_dir}"If any in-scope skill fails:
phase as buildingPrint a summary like:
Build stage complete for {plugin-name}
Target: {target_dir}/
Action: {create|modify}
Built:
- {skill-a}
- {skill-b}
Updated in place:
- {existing-skill-c}
Skipped:
- {unchanged-skill-d}
Next step:
Test each skill with 2-3 real scenarios, then iterate with skill-creator
When refined: /studio-quality:validate {target_dir}
Refinement tips:
- Test skills with real inputs, not just placeholders
- Use skill-creator to iterate on specific skills that need improvement
- Watch for edge cases: empty inputs, missing preconditions, large data sets
- If the plugin is hil-gated, test approval flows with realistic review scenarios
- If the plugin is stateful, verify workspace init and status tracking work end-to-end
- If the plugin is multi-pipeline, test each pipeline independently and with shared skills
npx claudepluginhub ameng2001/astra-studio-plugins --plugin studio-plannerScaffolds Claude Code plugin packages: gathers requirements, creates directory structure, generates manifest, adds initial skill and README, tests installation. Triggers on 'create plugin', 'new plugin', 'scaffold plugin'.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.