Menú
Interview the user to define a feature, then write a single feature definition file that downstream setup steps can consume.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | feature-define |
| description | Interview the user to define a feature, then write a single feature definition file that downstream setup steps can consume. |
Use this when a feature is not yet structured.
/tmp/feature-definition-<slug>.md.feature-setup.Keep the interview lean. Reuse answers the user already gave instead of re-asking them.
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.