skills.rest
giosuetedeschi-spec
giosuetedeschi-specCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Create standardized technical implementation plans with test-driven development steps.

Updated Jan 12, 2026
Search Tags:#workflow#planning#testing#tdd#development#architecture
One-click install
npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill writing-plans-giosuetedeschi-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/giosuetedeschi-spec/bobu-website/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/giosuetedeschi-spec/bobu-website --skill writing-plans-giosuetedeschi-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of disorganized or incomplete development by enforcing a structured, test-driven approach to feature implementation before any code is written.

Core Features & Use Cases

  • Bite-Sized Tasking: Breaks complex features into granular, 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 generate a standardized plan that guides a subagent through the exact file modifications, test writing, and commit cycles required to complete the task.

Quick Start

Invoke the writing-plans skill to generate a detailed implementation plan for the new authentication module.

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 TDD implementation plan for a new software feature?▼

To create a TDD implementation plan, break complex features into granular 2-5 minute actionable steps that mandate failing tests before implementation. This ensures strict adherence to test-driven development principles and precise file path referencing before code is written.

What is the best way to break down high-level requirements into development steps?▼

The best way to break down requirements is standardizing the transition from high-level architecture into granular, test-driven development steps within a dedicated worktree. This enforces atomic commit practices and precise file modifications for reliable feature execution.

How does test-driven development planning improve software architecture?▼

Test-driven development planning improves architecture by solving disorganized development through a structured approach. It mandates creating failing tests before implementation to guide exact file modifications, ensuring code quality and architectural reliability.

Can I use this planning workflow for atomic commits in a dedicated worktree?▼

Yes, this planning workflow requires strict adherence to atomic commit practices within a dedicated worktree. It facilitates the transition from high-level requirements to granular development steps, guiding subagents through precise test writing and commit cycles.

Do I need a dedicated worktree to execute a test-driven development plan?▼

A dedicated worktree is required to facilitate the transition from high-level requirements to granular, test-driven development steps. This isolated environment supports strict TDD principles, precise file path referencing, and atomic commit practices during implementation.

Related Skills

Explore More Software Engineering Skills→
ironbobironbob

writing-plans

Convert high-level specs into task-level implementation plans with file and test mappings.

Community
Intermediate
Rational-PartnersRational-Partners
4

tdd-workflow

Guide developers through red-green-refactor cycles with failing tests and refactoring.

Official
Intermediate
AnveioAnveio
1

task-rsid

Automate codebase improvement loops with verification pipelines and GitHub CLI PRs.

Community
Advanced
vKenjovKenjo

tlc-spec-driven

Guide projects through Specify, Design, Tasks, and Execute phases.

Community
Advanced