writing-plans

Generates detailed multi-task implementation plans from specs with TDD steps and commit checkpoints.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill writing-plans-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/writing-plans
Command: npx skills add https://github.com/Viranya2006/Lumen --skill writing-plans-viranya2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up too vague, placeholders slip in, and engineers without codebase context get stuck. This Skill produces a complete, bite-sized task breakdown that an engineer with zero project context can execute directly. ## Core Features & Use Cases - Structured Plan Documents: Generates plans with a mandatory header (goal, architecture, tech stack, global constraints) and per-task file lists, interfaces, and checkbox steps. - Bite-Sized TDD Tasks: Each task is decomposed into 2-5 minute steps following a write-failing-test, verify-failure, implement, verify-pass, commit cycle. - Placeholder Prevention & Self-Review: Enforces concrete code in every step and runs a self-review checklist for spec coverage, placeholder scans, and type consistency across tasks. - Execution Handoff: Offers subagent-driven or inline execution paths after the plan is saved to docs/superpowers/plans/. - Use Case: Given a feature spec for a new API endpoint, produce a dated plan file where each task lists exact files to create or modify, test code, run commands, and commit messages. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your spec before writing any code.

Frequently Asked Questions about writing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an implementation plan from a spec before coding?

Provide the spec or requirements and invoke the writing-plans skill before touching code. It produces a plan document with a goal, architecture, tech stack, global constraints, and per-task steps covering tests, implementation, and commits.

How to break a large feature spec into implementation tasks?

The skill first checks scope: if the spec spans multiple independent subsystems, it recommends splitting into separate plans, one per subsystem. Within a plan, tasks are right-sized so each ends with an independently testable deliverable.

What makes a good task granularity in an implementation plan?

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it to confirm failure, implementing minimal code, verifying the pass, and committing. Tasks fold setup and docs into the deliverable that needs them.

Where are implementation plan files saved?

Plans are saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md by default. User preferences for plan location override this default path.

When should I not use a single implementation plan?

Avoid one plan when the spec covers multiple independent subsystems that cannot each produce working, testable software on their own. In that case, break the work into separate plans during brainstorming, one per subsystem.