القائمة
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/.
التثبيت باستخدام 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>.
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.
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 | triage |
| description | 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/. |
The cheap, text-only first classification pass. See DESIGN.md §3.
issues/inbox/<id>/ (read issue.md)./tick) moves it.issue.md.bug | task | feature.trivial | standard | architectural.
trivial — localized, no design choices, reversible (docs, copy, a config value, an
obvious one-line fix).standard — looks like it fits existing patterns.architectural — the text already implies new structure (new module, dependency,
schema/contract change).type and difficulty into issue.md frontmatter.type: bug | task | feature
difficulty: trivial | standard | architectural # provisional
needsScoping: <bool>
needsScoping is false only when type != feature and difficulty == trivial
— the "obviously trivial" fast-path that skips Scoping and goes straight to ready/.
Features always need Scoping (they always require a Plan), so a feature is never
fast-pathed regardless of size.