skills.rest
dolutech
dolutechCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Plan multi-step software implementations from a spec and save them to docs/plans/YYYY-MM-DD-<feature-name>.md.

6|Updated Mar 7, 2026
Search Tags:#planning#tdd#documentation#software-engineering#task-breakdown#implementation-plan
One-click install
npx skills add https://github.com/dolutech/dolu-agents-skills --skill writing-plans-dolutech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/dolutech/dolu-agents-skills/tree/main/skills/writing-plans
Command: npx skills add https://github.com/dolutech/dolu-agents-skills --skill writing-plans-dolutech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document multi-step software implementations from a spec before coding, ensuring all decisions are captured and ready for execution.

Core Features & Use Cases

  • Structured implementation plans that describe required files, tests, docs, and verification steps.
  • DRY, YAGNI, and TDD driven workflows that promote small, safe commits.
  • Reusable templates saved to docs/plans/YYYY-MM-DD-<feature-name>.md for traceability and onboarding.

Quick Start

Plan a feature by drafting a detailed implementation plan that covers files touched, tests, docs, and verification.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I plan complex software features before coding to avoid ambiguity?▼

To plan complex software features without ambiguity, create a structured implementation plan that documents required files, tests, and verification steps. This ensures all decisions are captured and ready for execution before you start coding.

How do I break down a software implementation spec into safe, small commits?▼

Break down a software implementation spec into small commits by applying DRY, YAGNI, and TDD principles. This workflow enforces task breakdown with explicit file paths and testing strategies to ensure safe, incremental code commits.

What is the best way to document a multi-step task breakdown for onboarding and traceability?▼

The best way to document a multi-step task breakdown for traceability is saving reusable implementation plan templates to a structured path like docs/plans/YYYY-MM-DD-<feature-name>.md. This captures multi-step software implementations for onboarding.

Does TDD driven implementation planning work for complex codebases requiring thorough planning?▼

TDD driven implementation planning works for complex codebases by enforcing thorough planning before coding. It structures task breakdown and testing strategy, ensuring safe, incremental commits aligned with DRY and YAGNI principles.

When should I not use a structured implementation plan for software engineering tasks?▼

You should not use a structured implementation plan for simple, single-step modifications that require no task breakdown or testing strategy. It is designed for multi-step software implementations in complex codebases requiring thorough planning.

Related Skills

Explore More Software Engineering Skills→
blendsdkblendsdk
4

make_plan

Generate structured implementation plans for software features from user input.

Community
Advanced
jaydubya818jaydubya818

ce:work-beta

Execute work plan documents end-to-end with task generation and quality gates.

Community
Advanced
EntroVyxEntroVyx
3

plan

Generate structured markdown implementation plans with TDD-based steps.

Community
Intermediate
boparaiamritboparaiamrit
5

writing-plans

Convert high-level specs into task-based implementation plans with code blocks and verification steps.

Community
Advanced