القائمة
Bootstrap a Claude Code session by reading the feature workplan, latest journal entry, and open issues. Reports context to the user so they can confirm the session goal.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | session-start |
| description | Bootstrap a Claude Code session by reading the feature workplan, latest journal entry, and open issues. Reports context to the user so they can confirm the session goal. |
| user_invocable | true |
Read the following and report a concise summary to the user:
Identify the feature from the worktree name and branch:
basename $(pwd) and git rev-parse --abbrev-ref HEADRead the feature workplan:
docs/1.0/001-IN-PROGRESS/<feature-slug>/README.mddocs/1.0/001-IN-PROGRESS/<feature-slug>/workplan.mdRead the latest DEVELOPMENT-NOTES.md entry:
DEVELOPMENT-NOTES.md (last entry only)Read device notes if applicable:
SCSI-NOTES.md (last 2-3 entries)Read the session analysis report (if it exists):
data/sessions/report-all.md — look for the "LLM Session Analysis" sectionCheck open GitHub issues:
gh issue list --label <relevant-label> --state openCheck testing infrastructure (if the feature involves UI work):
TESTING.md for the overall test architecture (unit/ui/e2e categories)TESTING-UI.md for the UI test methodologysrc/pages/Test<Feature>Page.tsxtest/ui/<feature>.spec.tsReport to the user:
Do NOT start coding until the user confirms the session goal.