بنقرة واحدة
plan
Write an actionable markdown plan before implementation. Bite-sized tasks, exact paths, complete code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Write an actionable markdown plan before implementation. Bite-sized tasks, exact paths, complete code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Karpathy-inspired guidelines: Think before coding, Simplicity first, Surgical changes, Goal-driven execution
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Write clear Conventional Commits. Imperative subject, explain why not what, one logical change per commit.
Optimize based on measurement, never guesswork. Profile first, fix the real bottleneck, verify the win.
Refactor code without changing behavior. Small steps, green tests after every change, no mixing with feature work.
Review PRs on GitHub: read diffs, leave inline comments, approve or request changes.
| name | plan |
| description | Write an actionable markdown plan before implementation. Bite-sized tasks, exact paths, complete code. |
| conditional | true |
| paths | *.go,*.py,*.js,*.ts,*.rs,*.java,*.rb |
When asked to plan, do NOT implement code. Your deliverable is a markdown plan.
.cove/plans/YYYY-MM-DD_HHMMSS-<slug>.mdEach plan must include:
# [Feature Name] Implementation Plan
**Goal:** One sentence
**Architecture:** 2-3 sentences about approach
---
### Task N: [Name]
**Objective:** What this accomplishes
**Files:**
- Create: `exact/path/file.go`
- Modify: `exact/path/file.go:45-67`
**Step 1: Implementation**
[Exact code]
**Step 2: Verification**
Run: `go test ./path/...`
Expected: PASS
Tell the user the plan path and ask if they want execution to begin.
When using todowrite to convert a plan into executable tasks, declare dependencies
using the depends:<task-id> prefix in the content field:
depends:task-1 — single dependency, task runs after task-1 completesdepends:task-1,task-2 — multiple dependencies, task waits for alldepends: prefix — no dependencies, ready to execute immediatelyExample:
{
"todos": [
{"content": "Create auth middleware", "status": "pending", "priority": "high"},
{"content": "depends:task-1 Create auth tests", "status": "pending", "priority": "high"},
{"content": "depends:task-1,task-2 Wire up routes", "status": "pending", "priority": "medium"}
]
}
After defining tasks, call execute_plan with parallel=true to run independent tasks
concurrently. This respects the dependency graph automatically.