source-command-ff-create-plan

Creates detailed implementation plans through interactive codebase research and iterative user feedback.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-create-plan-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-ff-create-plan
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-create-plan
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-create-plan-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans without understanding the actual codebase leads to vague specs, missed edge cases, and scope creep. This Skill guides an AI agent through a structured, interactive process that grounds every plan in verified code research before writing a single line of the specification. ## Core Features & Use Cases - Codebase-Grounded Research: Spawns parallel research agents (codebase-locator, codebase-analyzer, thoughts-locator) to find relevant files, trace data flow, and return file:line references before planning begins. - Iterative Plan Development: Builds plans in stages—context gathering, research, outline approval, detailed writing—with user checkpoints at each step to allow course corrections. - Structured Plan Output: Writes plans to thoughts/shared/plans/ with a strict template covering current state, phased changes, automated vs. manual success criteria, and explicit out-of-scope items. - Use Case: Given a ticket like thoughts/allison/tickets/eng_1478.md describing parent-child tracking for sub-tasks, the Skill reads the ticket fully, researches the daemon codebase, presents design options, and produces a phased implementation plan with verifiable success criteria. ## Quick Start Ask the agent to create an implementation plan for a ticket file, for example: run ff_create_plan on thoughts/allison/tickets/eng_1234.md and iterate with me on the design.

Frequently Asked Questions about source-command-ff-create-plan

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

FAQPage Schema
How do I create an implementation plan from a ticket file?▼

Invoke the command with the ticket path, such as /ff_create_plan thoughts/allison/tickets/eng_1234.md. The agent reads the file fully, researches the codebase with parallel sub-tasks, then iterates with you on structure and details before writing the final plan.

How does the planning process research the codebase?▼

It spawns parallel specialized agents including codebase-locator to find relevant files, codebase-analyzer to explain implementation details, and thoughts-locator to surface prior research. All identified files are then read fully into the main context with file:line references.

Where are the generated implementation plans saved?▼

Plans are written to thoughts/shared/plans/ using the naming format YYYY-MM-DD-ENG-XXXX-description.md, where the ticket number is omitted if none exists. After writing, the thoughts directory is synced with humanlayer thoughts sync.

What makes a plan ready for implementation agents?▼

A ready plan contains no open questions, explicit out-of-scope items, and success criteria split into automated verification (make test, lint, typecheck commands) and manual verification (UI behavior, performance, edge cases). Each phase pauses for human confirmation before proceeding.

When should I not use this interactive planning workflow?▼

Avoid it for trivial changes like typo fixes where full research overhead adds no value, or when a complete plan already exists. The process is designed for features requiring design decisions, codebase investigation, and phased implementation.