Menu
Create feature infrastructure: branch, worktree, docs directory, and initial project documents derived from a feature definition.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run upfront discovery for a system-wide feature. Fans out discovery agents in parallel, synthesizes a strawman scope-manifest.yaml, writes the evidence trail to the feature docs directory.
Run targeted discovery for a mid-implementation operator complaint. Identifies all sibling surfaces consuming the same primitive/pattern; produces a widening proposal in the dispatch-wrapper-grammar format.
Use when shipping a new midi-macro-bridge version — bumping Cargo.toml, cutting a v-tag, publishing a GitHub Release, or updating the Homebrew tap.
Extend a feature's scope mid-implementation by adding new phases to the existing docs and issue plan without creating a new branch or worktree.
Explain the audiocontrol feature lifecycle and report the current state of active, in-progress, or partially defined features.
Wrap up a Codex work session by updating feature docs, recording development notes, and closing the loop on issue and hardware notes where needed.
| name | feature-setup |
| description | Create feature infrastructure: branch, worktree, docs directory, and initial project documents derived from a feature definition. |
Use this when the user wants to create the project-management scaffolding for a new feature.
/tmp/feature-definition-<slug>.md if it exists.git worktree add ~/work/audiocontrol-work/audiocontrol-<slug> -b feature/<slug>docs/1.0/001-IN-PROGRESS/<slug>/.prd.mdworkplan.mdREADME.mdimplementation-summary.mdDo not start implementation as part of setup.