القائمة
Use when you have a spec or requirements for a multi-step task. Covers both writing implementation plans and executing them task-by-task with review checkpoints.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.
Use when completing tasks, implementing major features, or before merging. Covers both performing self-review and responding to external review feedback.
Use when starting feature work needing isolation or when completing a development branch — covers worktree creation, setup, and branch finishing.
Use at the start of every conversation to establish skill-driven workflows. Ensures relevant skills are loaded before any action or response.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
| name | planning |
| description | Use when you have a spec or requirements for a multi-step task. Covers both writing implementation plans and executing them task-by-task with review checkpoints. |
Write comprehensive implementation plans assuming the engineer has zero codebase context and questionable taste. Document everything: which files to touch, complete code, testing, verification commands.
Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md
# [Feature Name] Implementation Plan
**Goal:** [One sentence]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies]
---
Each step is one action (2-5 minutes):
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
[Complete code]
**Step 2: Run test to verify it fails**
Run: `exact command`
Expected: FAIL with "specific message"
**Step 3: Write minimal implementation**
[Complete code]
**Step 4: Run test to verify it passes**
Run: `exact command`
Expected: PASS
**Step 5: Commit**
Use the todo tool:
action: create, name: "[Feature Name]"
Then batch add all tasks:
action: batch, items: [{ text: "Task 1: ...", group: "Phase 1" }, ...]
For each task:
todo start #Ntodo done #NAfter every 3 tasks, STOP and report:
Wait for human response before continuing.
After completing each task, before marking done:
Spec compliance:
Code quality:
Testing:
STOP executing immediately when:
Ask for clarification rather than guessing.
After all tasks verified:
todo summarygit-workflow skill for merge/PR options