writing-plans

Generates detailed multi-task implementation plans with TDD steps from a specification.

10|1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill writing-plans-flowing-abyss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/flowing-abyss/obsidian-local-fonts/tree/main/.ai/skills/writing-plans
Command: npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill writing-plans-flowing-abyss

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 blocks listing exact files to create or modify, interfaces consumed and produced, and checkbox steps. - TDD Bite-Sized Steps: Each task is decomposed into 2-5 minute steps following a test-driven cycle: write failing test, verify failure, implement minimally, verify pass, commit. - Placeholder Prevention and Self-Review: Enforces a no-placeholder policy (no TODOs or vague instructions) and runs a self-review checklist covering spec coverage, placeholder scans, and type consistency across tasks. - Use Case: After brainstorming a feature spec, invoke this Skill to produce a dated plan file under docs/superpowers/plans/, then hand it off to subagent-driven or inline execution workflows. ## Quick Start Ask the AI to use the writing-plans skill to turn your feature specification into a step-by-step implementation plan saved under docs/superpowers/plans/.

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 feature spec?

Provide the spec and invoke the writing-plans skill before touching code. It maps out the file structure, decomposes work into right-sized tasks with exact file paths, and writes each task as TDD checkbox steps saved to docs/superpowers/plans/.

What should a good implementation plan for AI coding agents include?

A plan should include a header with goal, architecture, tech stack, and global constraints, plus per-task blocks listing files to create or modify, interfaces consumed and produced, and concrete test-implement-commit steps with actual code, never placeholders.

How granular should tasks be in a coding implementation plan?

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it, implementing minimal code, and committing. Tasks themselves should be the smallest unit carrying their own test cycle and an independently testable deliverable.

When should a spec be split into multiple implementation plans?

Split when the spec covers multiple independent subsystems. Each plan should produce working, testable software on its own, so one plan per subsystem keeps scope reviewable and executable.

What are common mistakes when writing plans for engineers with no codebase context?

Common failures include placeholders like TODO or 'add error handling', references to undefined types or functions, inconsistent naming across tasks, and steps that describe what to do without showing the actual code.