writing-plans

Generate test-driven implementation plans with exact file paths and commands.

9|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CarbeneAI/Forge --skill writing-plans-carbeneai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/WritingPlans
Command: npx skills add https://github.com/CarbeneAI/Forge --skill writing-plans-carbeneai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates precise, developer-ready implementation plans that remove ambiguity from feature development by breaking work into tiny, verifiable tasks with exact file paths, complete code, and test-driven verification steps.

Core Features & Use Cases

  • Granular Task Breakdown: Splits features into 2-5 minute tasks so developers can make verifiable progress and parallelize work.
  • TDD-first Workflow: Requires tests before implementation, including expected failing outputs and subsequent green verification.
  • Exact Specifications: Provides exact file locations, complete runnable code, exact commands, expected output, and verification checklists.
  • Use Case: Prepare a deployment-ready plan for adding user authentication that includes tests, model code, endpoints, and verification curl commands saved to docs/plans/.

Quick Start

Ask the assistant to "Create an implementation plan for [feature] using TDD, include exact file paths, complete code, commands with expected output, and save the plan to docs/plans/YYYY-MM-DD-[feature].md".

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 implementation plan for a multi-step feature?

To create a test-driven implementation plan, break features into 2-5 minute granular tasks with exact file paths, complete runnable code, and TDD verification sequences. This removes ambiguity by providing exact commands and expected outputs for verifiable progress.

What is task breakdown granularity in TDD implementation plans?

Task breakdown granularity in TDD implementation plans splits software features into 2-5 minute steps. This sizing ensures developers make verifiable progress, parallelize work efficiently, and execute tests before writing implementation code.

How do I write implementation plans with exact file paths and runnable code?

Writing implementation plans with exact file paths requires specifying complete runnable code per task, exact commands with expected outputs, and verification checklists. Plans are saved to docs/plans/ as developer-ready markdown files for immediate execution.

Does this implementation plan approach work for complex authentication features?

Yes, this implementation plan approach works for complex features like user authentication by producing deployment-ready plans that include comprehensive tests, model code, endpoints, and verification curl commands saved to docs/plans/.

What's the best way to structure TDD sequences in a development roadmap?

The best way to structure TDD sequences in a development roadmap is requiring tests before implementation, including expected failing outputs and subsequent green verification. This ensures each granular task has verifiable, test-driven acceptance criteria.

When do I need an implementation plan with code specs and verification steps?

You need an implementation plan with code specs and verification steps when developing multi-step software features requiring exact file paths, complete runnable code, and developer-ready verification. It removes ambiguity by breaking work into tiny, verifiable tasks.