Menu
Show the feature lifecycle workflow, explain each skill's role, and report current state of any active or in-progress features.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | feature-help |
| description | Show the feature lifecycle workflow, explain each skill's role, and report current state of any active or in-progress features. |
| user_invocable | true |
Show the user the feature lifecycle and current state. Do NOT start any work — this is informational only.
Display this workflow:
/feature-define Interview to capture problem, scope, approach, tasks
│ Output: /tmp/feature-definition-<slug>.md
▼
/feature-setup Create branch, worktree, and docs from definition
│ Output: feature/<slug> branch, worktree, populated docs
▼
/feature-issues Create GitHub issues from workplan
│ Output: parent + implementation issues, workplan updated with links
▼
/feature-implement Execute workplan tasks via sub-agents
│
▼
/feature-review Code review of recent changes
│
▼
/feature-ship Verify acceptance criteria, run tests, create PR
│
▼
/feature-complete Move docs to 003-COMPLETE, update ROADMAP, close issues
│
▼
/feature-teardown Remove worktree and branch
Supporting skills:
/session-start — Bootstrap a session: read workplan, journal, issues, confirm goal/session-end — Write journal entry, update docs, commit/feature-pickup — Resume a feature in a new session (reads workplan + issue status)Detect and report the current state:
basename $(pwd) and git rev-parse --abbrev-ref HEADfeature/* branch, extract the slug and report which feature is activels docs/1.0/001-IN-PROGRESS/ to list all in-progress feature slugsgit worktree list | grep <slug>/tmp/feature-definition-<slug>.mdworkplan.mdls /tmp/feature-definition-*.md 2>/dev/null/feature-setup yet (no matching docs directory)## Current State
**Active worktree:** <slug> (or "none — on main")
**In-progress features:**
| Feature | Worktree | Definition | Docs | Issues | Next Step |
|---------|----------|------------|------|--------|-----------|
| <slug> | yes/no | yes/no | yes/no | yes/no | /feature-X |
**Pending definitions (not yet set up):**
- /tmp/feature-definition-<slug>.md → run `/feature-setup <slug>`
For the "Next Step" column, determine the earliest incomplete step:
/feature-define/feature-setup <slug>/feature-issues/feature-implement or /feature-pickupRun 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.