writing-plans

Generate structured, test-driven implementation plans for software development tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ambiguous or poorly structured development tasks by forcing a rigorous, test-driven, and bite-sized decomposition of any technical requirement.

Core Features & Use Cases

  • Task Decomposition: Breaks complex features into granular, testable steps that follow DRY and YAGNI principles.
  • Standardized Planning: Enforces a consistent document structure including architecture, tech stack, and global constraints.
  • Use Case: When starting a new feature, use this skill to generate a detailed roadmap that ensures every file modification and test case is clearly defined before a single line of production code is written.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user authentication module based on the provided requirements.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate a TDD-ready implementation plan for complex feature development?

To generate a TDD-ready implementation plan, decompose complex feature development into granular, testable steps that define architecture boundaries, tech stack constraints, and specific file modifications before writing production code.

What is the best way to break down ambiguous software engineering tasks into testable steps?

The best way to break down ambiguous software engineering tasks is applying rigorous task decomposition that enforces DRY and YAGNI principles, ensuring every file modification and test case is clearly defined.

How do I structure an implementation plan to ensure frequent commits and maintainable code output?

Structure an implementation plan using standardized documentation that includes architecture, tech stack, and global constraints, satisfying requirements for frequent commits and precise file-level instructions to ensure maintainable code output.

Can I use task decomposition to define architectural boundaries before writing production code?

Yes, you can use task decomposition to define clear architectural boundaries by generating a detailed roadmap that ensures every test case and file modification is specified before a single line of production code is written.

What should be included in a standardized planning document for software development tasks?

A standardized planning document for software development tasks should include architecture details, tech stack specifications, global constraints, and bite-sized testable steps following DRY and YAGNI principles.

When do I need a structured test-driven implementation plan for my software project?

You need a structured test-driven implementation plan when starting new features that require clear architectural boundaries and granular task decomposition to ensure high-quality, maintainable code output.