What problem does it solve?
This Skill turns an unstructured software backlog into an executable sprint plan, preventing unclear ownership, dependency deadlocks, merge conflicts, and unverifiable completion.
Core Features & Use Cases
- Parallel Work Planning: Assign independent tickets to iOS, Android, backend, design, QA, and review roles while sequencing dependent work.
- Dependency and Readiness Tracking: Capture ticket dependencies, shared surfaces, acceptance criteria, specification anchors, and touches notes before work begins.
- Auditable Board Management: Create and update the generated sprint board through an append-only event log with enforced state transitions, review gates, QA validation, cycle limits, and self-metrics.
- Use Case: For a mobile app backlog with platform-specific features and shared architecture work, use this Skill to launch independent tracks, serialize shared-file changes, and establish a verifiable definition of done.
Quick Start
Ask the sprint planner to convert the project backlog and implementation specifications into a dependency-aware sprint plan and validated board.
