plan

Convert approved designs into TDD-oriented tasks with exact file paths and verification commands.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CasaPerks/casaflow --skill plan-casaperks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/CasaPerks/casaflow/tree/main/core/skills/plan
Command: npx skills add https://github.com/CasaPerks/casaflow --skill plan-casaperks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an approved design or requirements into a step-by-step implementation plan that an engineer (or AI agent) can execute with minimal ambiguity.

Core Features & Use Cases

  • TDD-oriented task decomposition: Breaks work into bite-sized red-green-refactor tasks with verification steps and commits.
  • Exact file paths and change scope: Maps the file structure up front to reduce wrong-directory mistakes.
  • Flag-aware planning: Emits a required feature-flag task first when the spec indicates flag.decision: yes, ensuring safe gating.

Quick Start

Give your approved design and ask the AI to plan the implementation for a multi-step Jira ticket in your repo workflow.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn an approved design into a TDD implementation plan?

Implementation planning decomposes approved designs into bite-sized red-green-refactor tasks with exact file paths and verification commands. It reads configuration files for conventions and optionally generates flag tasks based on spec frontmatter.

What is feature flag task decomposition in spec-first planning?

Feature flag task decomposition emits a required feature-flag setup task first when the spec frontmatter indicates a flag decision. This ensures safe gating before generating the bite-sized implementation tasks for multi-step feature delivery.

How do I break down a multi-step Jira ticket into executable coding tasks?

Break down a multi-step Jira ticket by routing the approved design into the planner, which maps the repository file structure up front and outputs a concrete execution sequence of bite-sized tasks with exact paths to reduce wrong-directory mistakes.

Does the implementation planner enforce task granularity and prevent placeholder code?

Yes, the implementation planner enforces task granularity, requires a plan header, and prohibits placeholder code in the output. It ensures every task in the execution sequence has concrete file paths and verification commands.

Can I use my repo conventions and strategy preferences during task decomposition?

Yes, the planner reads the casaflow configuration file to align the generated execution sequence and verification steps with your established repo conventions and strategy preferences during task decomposition.

When do I need an implementation plan with exact file paths before touching code?

You need an implementation plan with exact file paths when executing a multi-step feature delivery that requires a concrete sequence of bite-sized TDD tasks. This minimizes ambiguity and prevents wrong-directory mistakes before touching code.