plan

Create TDD-driven implementation plans with tests, architecture, and risk mitigations.

15|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lionbenjamin/agent-templates --skill plan-lionbenjamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/plan
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill plan-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates technical implementation plans from high-level specifications, applying a disciplined, TDD-driven approach to ensure testability and traceability.

Core Features & Use Cases

  • TDD-driven plan generation: translates specs into testable implementation plans with clear milestones.
  • Verification strategy: defines tests, acceptance criteria, and risk mitigations to ensure correctness.
  • Use Case: convert a product spec into a phased development plan with concrete tasks, tests, and delivery milestones.

Quick Start

Provide a high-level spec and the Plan will generate the full TDD-driven implementation plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert a software specification into a TDD-driven implementation plan?

To convert a specification into a TDD-driven implementation plan, provide a high-level spec to generate a structured technical plan with defined test files, implementation changes, and delivery milestones.

What is the best way to structure test files and verification steps from a product spec?

Structuring test files and verification steps from a product spec requires applying a TDD-driven workflow that defines clear acceptance criteria, architecture milestones, and risk mitigations for software delivery.

Can I generate a phased development plan with concrete tasks and risk mitigations from a high-level spec?

Yes, you can generate a phased development plan with concrete tasks and risk mitigations from a high-level spec, ensuring testability and traceability through a disciplined TDD-driven approach.

Does this TDD planning approach require manual gates during execution?

No, this TDD planning approach produces a structured implementation plan designed to be executed with minimal manual gates, translating specifications directly into testable tasks and verification steps.

When do I need a TDD-driven technical implementation plan for software delivery?

You need a TDD-driven technical implementation plan when translating high-level specifications into phased development, ensuring correctness through defined tests, acceptance criteria, and structured risk mitigations.

How does TDD-driven plan generation ensure traceability from spec to implementation changes?

TDD-driven plan generation ensures traceability by translating high-level specifications into structured milestones with specific test files, architecture definitions, and implementation changes mapped to verification steps.