القائمة
Second pass over an Issue — explore the codebase, produce a candidate file list and deterministic signals, and FINALIZE Difficulty. Use for any Issue not fast-pathed as trivial by Triage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement a ready Issue inside its own git worktree, building only within existing architecture. Cord-pull to needs-plan if hidden architecture is discovered. Use when advancing an Issue out of issues/ready/.
Re-validate an Issue against current main and perform the real git merge to main. Merges are serialized (one at a time). Use after the Validation Pipeline passes (auto-merge) or after a human merge-review approves.
Co-author plan.md INTERACTIVELY with a human through an interview (grill-with-docs style) for a needs-plan Issue. Agents never author a Plan alone — this Skill is the human-input gate. Invoked by /plan <id>.
First pass over an inbox Issue — assign Type and a provisional Difficulty from the Issue text ALONE (no code exploration). Use when advancing an Issue out of issues/inbox/.
Run the pre-merge Validation Pipeline on an Issue's worktree — intent-judge, then tests, then deterministic checks — each with a bounded fix-and-retry loop. Use for an Issue in validating/, and again at merge time for re-validation.
| name | scoping |
| description | Second pass over an Issue — explore the codebase, produce a candidate file list and deterministic signals, and FINALIZE Difficulty. Use for any Issue not fast-pathed as trivial by Triage. |
The code-exploring pass that finalizes Difficulty and seeds the Plan. See DESIGN.md §3.
type and provisional difficulty set.app/ — find the files this Issue would touch./tick moves it.issue.md (and its provisional classification).app/ to build a candidate file list — the files you expect to change.standard, not architectural; a one-line change
that introduces a new public contract is architectural). Scoping may promote
standard → architectural.difficulty into frontmatter and append a ## Scoping section to
issue.md containing the candidate file list and the signals (this seeds the Plan).type: bug | task | feature
difficulty: trivial | standard | architectural # FINAL
candidateFiles: [ ... ]
route: ready | needs-plan
route is needs-plan when type == feature OR difficulty == architectural
(both require a human-authored Plan). Otherwise ready.