planning-and-roadmapping

You can convert scattered backlog items into a prioritized roadmap by collecting prompts, issues, and tasks, then normalizing them with descriptions, dependencies, and acceptance criteria. This structures your inputs into a living document aligned with project progress.

A living roadmap is a canonical document that continuously reflects ongoing progress and decisions. It maintains project documentation by cross-referencing artifacts and publishing summaries aligned with repository docs to keep everything updated as tasks evolve.

To normalize backlog items into structured tasks, the skill processes raw inputs like issues and prompts, then formats each item with clear descriptions, dependency tracking, acceptance criteria, and current statuses for comprehensive roadmap integration.

Yes, you can use outputs from planning or red-team sessions to seed a project roadmap. The skill collects these outputs alongside prompts and issues, integrating them directly into the prioritized roadmap as structured tasks.

The best way to update a canonical roadmap document is by prioritizing collected items and writing them to the master roadmap file, adding cross-references to related project artifacts to maintain a single source of truth for progress tracking.

Yes, this roadmap planning approach works without external dependencies. It operates independently to collect session inputs, normalize them into structured tasks, and update the canonical roadmap file directly within your repository documentation structure.