writing-plans

Translate software specs into file-aware implementation plans with test strategy.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill writing-plans-droxey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/droxey/skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/droxey/skills --skill writing-plans-droxey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, error-prone engineering work by converting requirements into a structured implementation plan before touching the codebase.

Core Features & Use Cases

  • Multi-step implementation planning: Produces a task-by-task plan with file-level guidance, sequencing, and commit checkpoints.
  • Spec-to-execution handoff: Creates an engineering-ready document that assumes the implementer has little context and may need strong assumptions spelled out.
  • TDD-focused workflow: Enforces bite-sized steps that include writing failing tests, running them, implementing minimally, and re-running tests.

Quick Start

Use the writing-plans skill to create an implementation plan for a multi-step feature from a spec or requirements document.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn software specs into an executable implementation plan?▼

To turn software specs into an executable implementation plan, you decompose requirements into bite-sized, file-aware tasks with explicit execution order, commit checkpoints, and test strategies. This structured approach prevents slow engineering work.

What is a spec-to-code engineering workflow?▼

A spec-to-code engineering workflow translates requirements into an implementation-ready document with decomposed tasks and explicit handoff. It assumes the implementer lacks context, spelling out strong assumptions for safe execution.

How do I plan multi-step feature development with TDD?▼

Plan multi-step feature development with TDD by sequencing bite-sized steps that include writing failing tests, running them, implementing minimally, and re-running tests. This enforces a clear, test-driven execution order.

Can I use task decomposition for subagent-driven planning?▼

Yes, you can use task decomposition for subagent-driven planning by generating a standardized plan format with decomposed tasks, no placeholders, and explicit execution handoff to guide subagents safely.

What is the best way to document task sequencing for feature implementation?▼

The best way to document task sequencing for feature implementation is creating a file-aware plan with commit checkpoints and documentation touchpoints. This provides strong execution order context for the implementer.

Why does my multi-step feature implementation lack clear execution order?▼

Multi-step feature implementation lacks clear execution order without a standardized plan format. Converting specs into bite-sized, file-aware tasks with explicit execution handoff resolves this slow, error-prone workflow.