skills.rest
unclehowell
unclehowellCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate step-by-step implementation plans with file paths, code, and TDD tasks.

Updated Sep 1, 2021
Search Tags:#workflow#planning#tdd#task-breakdown#developer-docs#subagent-driven-development#implementation-plans
One-click install
npx skills add https://github.com/unclehowell/unclehowell --skill writing-plans-unclehowell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/unclehowell/unclehowell/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/unclehowell/unclehowell --skill writing-plans-unclehowell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many multi-step engineering tasks arrive as vague specs or high-level requirements and lack the concrete, testable, and file-level instructions developers need to implement them reliably; this Skill eliminates guesswork by producing end-to-end, copy-pasteable implementation plans.

Core Features & Use Cases

  • Bite-sized TDD tasks: Breaks features into 2-5 minute tasks with failing tests, minimal implementations, and verification steps.
  • Complete file-level guidance: Specifies exact file paths to create or modify, with full code examples and line references when appropriate.
  • Verification and commits: Includes exact commands, expected outputs, and commit guidance to ensure reproducible progress and frequent commits.
  • Use Case: Preparing a delegated implementation for a subagent or a new contributor who has no context about the codebase.

Quick Start

Create an implementation plan for the new authentication feature that lists each file to add or modify, includes a failing test and minimal implementation for each step, exact commands to run, and verification steps.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn feature specs into step-by-step implementation plans?▼

Implementation plans transform vague specs into executable steps by specifying exact file paths, copy-pasteable code examples, TDD cycles, verification commands, commit guidance, and bite-sized tasks sized for 2-5 minute work items.

What is the best way to break down complex refactoring tasks for developers lacking context?▼

Task breakdown for complex refactors involves generating end-to-end, copy-pasteable implementation plans that include failing tests, minimal implementations, exact commands to run, and verification steps to ensure reproducible progress and frequent commits.

Can I generate TDD workflow plans for delegated subagent development?▼

Yes, subagent-driven development workflows are supported by producing comprehensive, step-by-step implementation plans that provide delegated implementers with complete file-level guidance, exact file paths, and full code examples.

Does implementation planning work for multi-step feature development without existing developer docs?▼

Implementation planning eliminates guesswork for multi-step feature development by producing end-to-end plans with exact file paths, full code examples, line references, TDD cycles, and verification commands when developer documentation is lacking.

How do I create bite-sized TDD tasks for new contributors?▼

Bite-sized TDD tasks are created by breaking features into 2-5 minute work items that include failing tests, minimal implementations, exact commands to run, expected outputs, and commit guidance to ensure reproducible progress.

When should I not use automated implementation plans for software engineering tasks?▼

Automated implementation plans are designed for multi-step engineering tasks, complex refactors, and delegated subagent workflows; single-step tasks or trivial changes requiring no file-level guidance or TDD cycles do not need this structured planning approach.

Related Skills

Explore More Software Engineering Skills→
forketyforkforketyfork
2

airtight-plans

Convert vague project tasks into structured Markdown implementation plans.

Community
Basic
DarkArty07DarkArty07
3

writing-plans

Generate structured implementation plans with exact file paths and TDD cycles.

Community
Advanced
JoeCP17JoeCP17
8

writing-plans

Convert software requirements into test-first engineering implementation plans.

Community
Intermediate
jaredcroxtonjaredcroxton

writing-plans

Generate implementation plans with TDD task sequencing and exact file paths.

Community
Advanced