skills.rest
xleliberty
xlelibertyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate test-driven implementation plans with task decomposition for software development.

Updated Nov 3, 2016
Search Tags:#planning#tdd#development#implementation#software-engineering#task-decomposition
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill writing-plans-xleliberty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-plugins-official/superpowers/5.0.7/skills/writing-plans
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill writing-plans-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of disorganized or incomplete software development by enforcing a rigorous, test-driven implementation plan before any code is written.

Core Features & Use Cases

  • Task Decomposition: Breaks complex features into bite-sized, 2-5 minute actionable steps.
  • TDD Enforcement: Mandates the creation of failing tests before implementation to ensure code quality and reliability.
  • Use Case: When starting a new feature, use this skill to map out exactly which files to modify, what tests to write, and how to verify the implementation, ensuring the engineer has a clear, step-by-step roadmap.

Quick Start

Use the writing-plans skill to generate 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 create a test-driven development plan for a complex software feature?▼

To create a test-driven development plan, you decompose complex software features into granular, 2-5 minute actionable steps and mandate failing tests before implementation to ensure structured, reliable code delivery.

What is task decomposition in software engineering and when do I need it?▼

Task decomposition in software engineering breaks complex features into bite-sized, 2-5 minute actionable steps. It is needed for complex coding projects requiring clear architectural decomposition and step-by-step execution guidance.

How do I ensure my implementation plan enforces TDD and DRY principles?▼

To ensure your implementation plan enforces TDD and DRY principles, mandate the creation of failing tests before implementation and structure granular task tracking to verify code quality and reliable delivery.

Can I use this approach to map out exactly which files to modify for a new module?▼

Yes, you can use this approach to map out exactly which files to modify, what tests to write, and how to verify the implementation, ensuring the engineer has a clear, step-by-step roadmap.

What is the best way to structure an implementation plan for complex coding projects?▼

The best way to structure an implementation plan for complex coding projects is by applying rigorous architectural decomposition to generate step-by-step execution guidance, breaking down tasks into 2-5 minute actionable steps.

Related Skills

Explore More Software Engineering Skills→
markshustmarkshust
55

plan-create

Generate structured implementation plans with task breakdowns and TDD requirements.

Community
Advanced
yellow-seedyellow-seed

test-driven-development

Guide Red-Green-Refactor cycles for test-driven development workflows.

Community
Basic
manuelbrandner85manuelbrandner85

writing-plans

Generate test-driven implementation plans with granular task decomposition for software features.

Community
Intermediate
MichelMokbelMichelMokbel

github-project-management

Coordinate GitHub issue tracking with multi-agent swarm orchestration.

Community
Advanced