create-plan

Create a test-first implementation plan from a spec or issue.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill create-plan-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-plan
Command: npx skills add https://github.com/gittower/git-flow-next --skill create-plan-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Read, Grep, Glob, Write, Bash, mcp__github__get_issue.

What problem does it solve?

This Skill helps you convert a spec, analysis, or feature concept into a structured implementation plan before any coding begins, reducing ambiguity and preventing missed edge cases.

Core Features & Use Cases

  • Test-First Planning: Builds the test scenarios before implementation so the desired behavior is clear and measurable.
  • Implementation Breakdown: Translates scenarios into ordered coding tasks with file-level guidance.
  • Workflow Guidance: Helps align planning with repository conventions, testing rules, and documentation updates.
  • Use Case: A developer receives a GitHub issue for a new feature and uses this Skill to produce a plan that can be reviewed, validated, and executed safely.

Quick Start

Ask the assistant to create a test-first implementation plan from your spec or issue using the repository context.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create a test-first implementation plan from a GitHub issue?

To create a test-first implementation plan from a GitHub issue, this Skill reads the issue and repository context to produce ordered coding tasks with scenario-based test designs and file-level guidance. It structures the entire workflow before coding begins.

What is test-first planning in software engineering?

Test-first planning is defining test scenarios and desired behaviors before writing any implementation code. This approach ensures the desired behavior is clear, measurable, and aligned with repository conventions before development starts.

How do I break down a software feature spec into ordered coding tasks?

You can break down a feature spec into ordered coding tasks by translating analysis scenarios into file-level code changes, documentation updates, and review checkpoints. This ensures a structured, repository-aware task breakdown.

Can I align my implementation plan with existing repository conventions?

Yes, the implementation plan aligns with existing repository conventions by reading project guidelines and applying repository-aware task breakdowns. It ensures tests, code changes, and documentation match your established workflow rules.

Does this planning approach handle edge cases in software development?

Yes, this test-first planning approach reduces ambiguity and prevents missed edge cases by building test scenarios before implementation. It validates expected behaviors against repository context early in the process.

What's the best way to turn a concept into an executable coding plan?

The best way to turn a concept into an executable coding plan is to generate a structured breakdown covering tests, code changes, and review checkpoints. This allows the plan to be reviewed, validated, and executed safely.