القائمة
Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.
Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".
Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.
Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.
Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.
Test-driven development workflow for Rust. Use before writing any implementation code — write a failing test first, then implement, then refactor.
| name | writing-plans |
| description | Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design. |
A plan is a complete implementation guide a fresh agent with no prior context could execute. If it requires context not in the document, it is incomplete.
Save to: docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md
Structure:
# <Title>
> **For agentic workers:** Run `/godmode:tackle-issues` to dispatch parallel
> subagents per task group. Use `/godmode:test-driven-development` for each
> implementation step. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** One sentence.
**Architecture:** Crates/files affected, data flow.
**Tech Stack:** Rust edition, key crates.
**Repo:** `/path/to/repo`
**GitHub issue:** #N (if applicable)
---
## Task 1: <name>
**Files:**
- `path/to/file.rs`
- [ ] **Step 1:** ...
- [ ] **Step 2:** ...
- [ ] **Commit:** `git commit -m "feat: ..."`
---
## Verification Checklist
- [ ] All tasks complete
- [ ] cargo check passes
- [ ] cargo clippy -- -D warnings clean
Create .ctx/tasks/<YYYYMMDD>-<feature-name>.yaml in the repo root.
Schema:
id: <feature-name> # kebab-case, no date prefix
title: "<plan title>"
plan_file: docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md
date: YYYY-MM-DD
repo: <repo dirname>
github_issue: N # null if none
status: pending # pending | in_progress | done
tasks:
- id: t1
title: "<task 1 title>"
status: pending # pending | in_progress | done | blocked
depends_on: []
files:
- path/to/file.rs
- id: t2
title: "<task 2 title>"
status: pending
depends_on: [t1]
files: []
commits: []
Rules:
## Task N: section in the markdowndepends_on mirrors the sequential order of tasks unless explicitly independentstatus starts as pending for all tasksYYYYMMDD-<feature-name>.yaml
where YYYYMMDD is today's datepython3 -c "import yaml; yaml.safe_load(open('.ctx/tasks/<file>'))" if unsure