writing-plans

Generate structured implementation plans with task dependencies and validation commands.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill writing-plans-byronwilliamscpa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill writing-plans-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates context gaps, inconsistent implementation, and costly rework that occur when engineers execute multi-step development tasks without a clear, codebase-aligned plan.

Core Features & Use Cases

  • Codebase Discovery Guidance: Systematically identifies existing files, patterns, and reusable utilities to avoid duplicate work and ensure alignment with repository conventions.
  • Bite-Sized Task Decomposition: Breaks complex specs into 2-5 minute actionable steps with clear dependencies, exact test commands, and commit guidelines following TDD, DRY, and YAGNI principles.
  • Use Case: When handed a spec for adding a new user authentication feature, this Skill generates a complete plan with failing tests, implementation steps, and validation commands tailored to your repo's structure, so engineers can execute without prior context of the codebase.

Quick Start

Share your feature spec or multi-step development requirements with the writing-plans skill to receive a complete, actionable implementation plan aligned with your codebase's conventions.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan for a complex new feature in an existing codebase?

To generate an implementation plan for an existing codebase, you provide a feature specification and the tool produces bite-sized, 2-5 minute task steps with clear dependencies. This ensures repository alignment and eliminates context gaps during multi-step development.

What is the best way to break down a large development spec into TDD tasks?

Breaking down a development spec into TDD tasks involves decomposing the requirements into 2-5 minute actionable steps. The plan includes failing tests, implementation steps, and exact validation commands to ensure test-driven development adherence and prevent rework.

How do I align new code with existing repository conventions before coding?

Aligning new code with repository conventions requires systematic codebase discovery to identify existing patterns and reusable utilities. This process prevents duplicate work and ensures your implementation plan follows DRY and YAGNI principles.

Can I generate a step-by-step refactoring plan with exact test commands?

Yes, you can generate a step-by-step refactoring plan that includes exact test commands and commit guidelines. The plan structures the refactor into actionable tasks with clear dependencies to maintain test-driven development validation throughout the workflow.

When do I need a pre-implementation plan for a bug fix?

You need a pre-implementation plan for a bug fix when executing multi-step development tasks in an existing codebase. Planning eliminates context gaps and inconsistent implementation by providing repository-aligned task dependencies and validation commands.

Does implementation planning work without prior context of the codebase?

Yes, implementation planning works without prior codebase context by using codebase discovery guidance to systematically identify existing files and patterns. This allows engineers to execute tailored plans with exact validation commands regardless of prior familiarity.