FP Planning
FP Planning Skill
Plan creation and breakdown patterns for the FP CLI
Core Planning Concepts
Plans as Issues
Key insight: In FP, plans are just elaborate issues. There's no separate "plan" entity.
A plan is an issue that:
- Has a comprehensive description (the plan document)
- Has child issues (the tasks/sub-tasks)
- May have dependencies between children
- Starts with status "todo" and transitions to "done" when all children are done
Issue Hierarchy
More from fiberplane/claude-code-plugins
fp-plan
Create and break down plans into trackable issues. Use when user asks to "create a plan", "break down feature", "design implementation", "structure this work", or pastes a Linear/GitHub/Notion URL to import.
52fp-implement
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
49fp-review
Review code, create stories, and ensure commits are assigned to issues. Use when user asks to "review code", "assign commits", "check commits are assigned", "prepare for review", "create a story", or "write a story".
48fp workflow
This skill should be used when the user asks to "start working on issue", "what should I work on", "pick up task", "continue work", "find next task", "hand off", or "end session". Provides agent work session patterns for the FP CLI including claiming work, logging progress, and VCS-based change tracking.
2fp review
Review code, create stories, and ensure commits are assigned to issues. Use when user asks to "review code", "assign commits", "check commits are assigned", "prepare for review", "create a story", or "write a story".
2