Plan Writing
- 834 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
plan-writing is a task-planning skill that turns vague feature ideas or refactoring needs into short ordered task lists with verification steps for developers who need agent-executable implementation plans.
About
plan-writing provides a structured framework—sourced from obra/superpowers—for breaking multi-step work into clear, actionable tasks with verification criteria. Each task targets a 2–5 minute outcome with one verifiable result, explicit dependencies, and checks for done-ness including expected outputs and tests. Developers reach for plan-writing when implementing features, refactoring codebases, or any work requiring ordered steps an coding agent can follow without ambiguity. The skill emphasizes small focused tasks, clear verification, and independently checkable outcomes rather than high-level roadmaps.
- Breaks work into 5-10 small tasks that take 2-5 minutes each
- Every task includes independent verification criteria and expected output
- Identifies dependencies, parallel work, and critical path
- Saves plans as {task-slug}.md directly in project root
- Dynamic per-task planning with no fixed templates
Plan Writing by the numbers
- 834 all-time installs (skills.sh)
- +22 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #557 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill plan-writingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 834 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you write agent-executable task plans?
Turn vague feature ideas or refactoring needs into short, ordered task lists with clear verification steps that an agent can execute.
Who is it for?
Developers delegating multi-step features or refactors to coding agents who need granular, verifiable task breakdowns.
Skip if: Developers needing architecture diagrams, PRD authoring, or long-range roadmaps should skip plan-writing because it targets short executable task lists.
When should I use this skill?
User asks to plan a feature, refactor, or multi-step implementation with clear verification steps.
What you get
Ordered task list with dependencies, verification criteria, and expected outputs per step.
- Ordered task list
- Per-task verification criteria
- Dependency map
By the numbers
- Each planned task targets 2–5 minutes of work
- Three core breakdown principles: small tasks, clear verification, dependencies
Files
Plan Writing
Source: obra/superpowers
Overview
This skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.
Task Breakdown Principles
1. Small, Focused Tasks
- Each task should take 2-5 minutes
- One clear outcome per task
- Independently verifiable
2. Clear Verification
- How do you know it's done?
- What can you check/test?
- What's the expected output?
3. Logical Ordering
- Dependencies identified
- Parallel work where possible
- Critical path highlighted
- Phase X: Verification is always LAST
4. Dynamic Naming in Project Root
- Plan files are saved as
{task-slug}.mdin the PROJECT ROOT - Name derived from task (e.g., "add auth" →
auth-feature.md) - NEVER inside
.claude/,docs/, or temp folders
Planning Principles (NOT Templates!)
🔴 NO fixed templates. Each plan is UNIQUE to the task.
Principle 1: Keep It SHORT
| ❌ Wrong | ✅ Right |
|---|---|
| 50 tasks with sub-sub-tasks | 5-10 clear tasks max |
| Every micro-step listed | Only actionable items |
| Verbose descriptions | One-line per task |
Rule: If plan is longer than 1 page, it's too long. Simplify.
---
Principle 2: Be SPECIFIC, Not Generic
| ❌ Wrong | ✅ Right |
|---|---|
| "Set up project" | "Run npx create-next-app" |
| "Add authentication" | "Install next-auth, create /api/auth/[...nextauth].ts" |
| "Style the UI" | "Add Tailwind classes to Header.tsx" |
Rule: Each task should have a clear, verifiable outcome.
---
Principle 3: Dynamic Content Based on Project Type
For NEW PROJECT:
- What tech stack? (decide first)
- What's the MVP? (minimal features)
- What's the file structure?
For FEATURE ADDITION:
- Which files are affected?
- What dependencies needed?
- How to verify it works?
For BUG FIX:
- What's the root cause?
- What file/line to change?
- How to test the fix?
---
Principle 4: Scripts Are Project-Specific
🔴 DO NOT copy-paste script commands. Choose based on project type.
| Project Type | Relevant Scripts |
|---|---|
| Frontend/React | ux_audit.py, accessibility_checker.py |
| Backend/API | api_validator.py, security_scan.py |
| Mobile | mobile_audit.py |
| Database | schema_validator.py |
| Full-stack | Mix of above based on what you touched |
Wrong: Adding all scripts to every plan Right: Only scripts relevant to THIS task
---
Principle 5: Verification is Simple
| ❌ Wrong | ✅ Right |
|---|---|
| "Verify the component works correctly" | "Run npm run dev, click button, see toast" |
| "Test the API" | "curl localhost:3000/api/users returns 200" |
| "Check styles" | "Open browser, verify dark mode toggle works" |
---
Plan Structure (Flexible, Not Fixed!)
# [Task Name]
## Goal
One sentence: What are we building/fixing?
## Tasks
- [ ] Task 1: [Specific action] → Verify: [How to check]
- [ ] Task 2: [Specific action] → Verify: [How to check]
- [ ] Task 3: [Specific action] → Verify: [How to check]
## Done When
- [ ] [Main success criteria]That's it. No phases, no sub-sections unless truly needed.
Keep it minimal. Add complexity only when required.
Notes
[Any important considerations]
---
## Best Practices (Quick Reference)
1. **Start with goal** - What are we building/fixing?
2. **Max 10 tasks** - If more, break into multiple plans
3. **Each task verifiable** - Clear "done" criteria
4. **Project-specific** - No copy-paste templates
5. **Update as you go** - Mark `[x]` when complete
---
## When to Use
- New project from scratch
- Adding a feature
- Fixing a bug (if complex)
- Refactoring multiple files
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use plan-writing for granular agent-ready task lists; use architecture or PRD skills when you need system design or product requirements first.
FAQ
How long should each task be in plan-writing?
plan-writing specifies tasks that take 2–5 minutes each with one clear outcome. Every task includes verification criteria describing how to confirm completion, what to test, and the expected output.
When should plan-writing be invoked?
plan-writing fits feature implementation, refactoring, or any multi-step work needing structured breakdowns. The skill adds dependencies and verification steps so coding agents can execute tasks independently.
Is Plan Writing safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.