القائمة
Reads the capability specs changed on this branch and writes a technical plan. Optional — skip for straightforward changes and go straight to /code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | plan |
| description | Reads the capability specs changed on this branch and writes a technical plan. Optional — skip for straightforward changes and go straight to /code. |
| model | opus |
| disable-model-invocation | true |
Translates spec changes on the current branch into a technical plan. Use for non-trivial features where the approach warrants discussion before coding starts.
$ARGUMENTS — an optional issue ID or slug used to name the plan directory (e.g. MXB-7).
If empty, derives from the branch name.
git diff main --name-only -- specs/
Read each changed spec file in full. Then read the diff to understand what is new:
git diff main -- specs/<feature>/spec.md
If no specs have changed on this branch, tell the user and stop.
If $ARGUMENTS is provided: changes/<arguments>-<feature>/plan.md
Otherwise derive from branch name: changes/<branch-slug>/plan.md
# Plan: <Title>
**Spec:** `specs/<feature>/spec.md`
**Branch:** `<branch>`
## Approach
<Technical description. What components, server functions, data flow, state management.
1-3 paragraphs.>
## File Changes
| File | Action | Notes |
|------|--------|-------|
| `src/features/<feature>/...` | create | ... |
## Decisions
<Key technical choices and why this approach over alternatives. Omit if nothing significant.>
Warranted when the plan involves a new dependency, a change to established architecture, a new pattern being introduced for the first time, or a decision future developers would otherwise re-litigate.
ls docs/adr/*.md 2>/dev/null | wc -l
Create docs/adr/NNNN-<slug>.md using MADR v3 format. Skip if none of the above apply.
Run /simplify to review the plan and ADR for clarity, redundancy, and quality.
git add changes/ docs/adr/
git commit -m "docs: plan <slug>"
Print:
/code has started — create a new entry if the approach changesImplements the feature changes introduced by spec changes on the current branch. Writes tests, runs quality checks, and commits.
End-to-end delivery skill — takes a Linear issue ID or a description, runs the appropriate pipeline (spec → plan → code → review), and handles all git and Linear orchestration.
Writes or updates the capability spec for the current feature branch from a prose description or context file passed via $ARGUMENTS.
PR review skill — fetches active GitHub Copilot review comments on a PR, critically evaluates each suggestion, implements those that improve code posture, and dismisses those that don't add value.