feature-plan

Convert feature specifications into TDD implementation plans with incremental pull request breakdowns.

1|Updated Jan 8, 2026

Search Tags:#tdd #test strategy #feature planning #spec review #rails #gherkin #pull request breakdown

Ready to run

npx skills add https://github.com/LaunchPadLab/ai-bank --skill feature-plan-launchpadlab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-plan
Source: https://github.com/LaunchPadLab/ai-bank/tree/main/claude/skills/feature-plan
Command: npx skills add https://github.com/LaunchPadLab/ai-bank --skill feature-plan-launchpadlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It converts a feature specification into a concrete TDD implementation plan, so teams can move from ambiguous requirements to an actionable sequence of independently testable pull requests.

Core Features & Use Cases

Spec-to-plan analysis: Reads objectives, user stories, acceptance criteria, and Gherkin scenarios to extract test-driving details.
Component-first architecture planning: Identifies models, migrations, services, forms, controllers, policies, jobs, mailers, components, and views to clarify scope.
Incremental PR sequencing: Produces a staged PR plan ordered by dependencies (DB → logic → auth → endpoints → UI → notifications) with verification guidance for TDD.

Quick Start

Tell your AI assistant: analyze this feature spec and produce a TDD implementation plan with an incremental PR breakdown and specialist agent assignments.

Frequently Asked Questions about feature-plan

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

FAQPage Schema

How do I turn a feature specification into a TDD implementation plan?▼

To turn a feature specification into a TDD implementation plan, the feature spec is analyzed to extract test-driving details from objectives and Gherkin scenarios. It outputs a structured, incremental pull request sequence ordered by dependencies like database, logic, and UI layers.

What is the best way to break down Rails feature work into incremental pull requests?▼

Breaking down Rails feature work into incremental pull requests is best achieved by ordering tasks by dependencies: DB migrations, logic, auth, endpoints, UI, and notifications. This component-first approach clarifies scope and ensures each PR is independently testable.

How do I verify spec readiness before starting TDD feature planning?▼

Spec readiness for TDD feature planning is verified by checking the feature-review score and ensuring Gherkin scenarios are present. This confirms the specification contains enough detail to extract component scope and drive test development for Rails applications.

Does feature planning with Gherkin scenarios support assigning tasks to specialist agents?▼

Yes, feature planning with Gherkin scenarios supports assigning tasks to specialist agents. The generated implementation plan maps component architecture like models, services, and controllers to specific agents for structured development and testing.

What components are identified when planning a new feature for a Rails app?▼

When planning a new feature for a Rails app, identified components include models, migrations, services, forms, controllers, policies, jobs, mailers, and views. This component-first architecture planning clarifies the exact scope of the implementation work.

When should I not use a spec-to-plan TDD workflow for feature breakdown?▼

You should not use a spec-to-plan TDD workflow when your feature specification lacks Gherkin scenarios or acceptance criteria. Without verified spec readiness, the tool cannot accurately extract component scope or sequence incremental pull requests.