Menu
Create feature infrastructure: git branch, worktree, docs directory, and delegate documentation creation to documentation-engineer agent.
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: git branch, worktree, docs directory, and delegate documentation creation to documentation-engineer agent. |
| user_invocable | true |
This skill automates creating the infrastructure for a new feature. When invoked:
Determine feature slug and read definition:
/tmp/feature-definition-<slug>.md — if it exists, read it and use its contents to populate the docs with real content (not just templates)/feature-define <slug> first for better resultsCreate branch and worktree:
git worktree add ~/work/audiocontrol-work/audiocontrol-<slug> -b feature/<slug>
Create docs directory:
mkdir -p docs/1.0/001-IN-PROGRESS/<slug>
Delegate documentation creation:
docs/1.0/001-IN-PROGRESS/<slug>/prd.md — PRD from definition file's Problem Statement, Acceptance Criteria, Out of Scope, and Open Questions. If no definition file, use template.docs/1.0/001-IN-PROGRESS/<slug>/workplan.md — workplan from definition file's Implementation Phases, Technical Approach, and Dependencies. Include GitHub Tracking section (to be filled by /feature-issues). If no definition file, use template.docs/1.0/001-IN-PROGRESS/<slug>/README.md — status table with phases from definition filedocs/1.0/001-IN-PROGRESS/<slug>/implementation-summary.md — draft template for post-completion reportReport results:
feature/<slug>~/work/audiocontrol-work/audiocontrol-<slug>docs/1.0/001-IN-PROGRESS/<slug>//feature-issues