FFT-Project-Manager - Task Breakdown and Sprint Planning
Overview
Section titled “Overview”FFT-Project-Manager turns a feature request into a ready-to-execute plan. It breaks features into tasks, creates the GitHub milestone and issue structure, sequences dependencies, and keeps the backlog aligned with FlowForge’s ticket-first workflow (Rule #5). Triggered by the flowforge:project:plan Claude Code slash command (defined under commands/flowforge/project/plan.md) and by any large-scope request that requires decomposition.
Capabilities
Section titled “Capabilities”- Feature decomposition: splits epics into stories and stories into granular, independently shippable tasks.
- GitHub structure: creates milestones, labels, and issues with consistent templates and acceptance criteria.
- Sprint planning: estimates effort, balances capacity, and proposes sprint compositions.
- Dependency sequencing: identifies blocking relationships and proposes execution order.
- Milestone quality seal: always appends a final gap-analysis ticket per the FlowForge milestone-quality rule.
- Risk identification: surfaces delivery risks and proposes mitigations before the sprint starts.
- Version planning: coordinates semver transitions with tickets, release notes, and migration plans.
- Backlog hygiene: closes stale items, merges duplicates, keeps priorities current.
When to Use
Section titled “When to Use”- Kicking off a new milestone that needs a full ticket breakdown.
- Planning the next sprint from an existing backlog.
- Auditing an in-flight milestone to recover slipping scope.
- Creating the gap-analysis ticket that seals a milestone.
Example Prompts
Section titled “Example Prompts”"Break the user-profile feature into implementation tickets and create the v2.3 milestone""Plan next week's sprint using the current open backlog and a two-developer capacity""Create the final gap-analysis ticket for milestone v1.15 and summarize outstanding risks"