Convert sprint architecture and user stories into spec.md and plan.md files.
npx skills add https://github.com/robconery/crap-code --skill pm-robconery
Please help me install this Agent Skill. Skill: pm Source: https://github.com/robconery/crap-code/tree/main/.pi/skills/pm Command: npx skills add https://github.com/robconery/crap-code --skill pm-robconery
Breaks complex sprint architecture into clear, trackable tasks and wave-based execution plans, then keeps sprint documentation accurate and audit-friendly.
Use the pm skill with your sprint inputs to generate spec.md and plan.md with wave assignments, file ownership, and reviewer-enforced constraints.
High-intent search queries and answers about installing and using this skill.
Sprint planning tools convert architecture and user stories into an execution-ready specification and a wave-based task plan. This process breaks complex sprint architecture into clear, trackable tasks with non-overlapping file ownership per wave.
Wave planning is a task decomposition method that groups tasks into execution waves, enforcing parallelization rules where tasks in the same wave never touch the same files. Every task must declare file ownership up front to prevent merge conflicts during parallel execution.
Generate sprint specifications by consolidating sprint inputs into a spec.md file and a plan.md file with wave assignments and file ownership. This living documentation maps each task to acceptance criteria and requires task logging for drafted tasks and doc proposals.
Yes, sprint planning workflows map each task directly to acceptance criteria within the generated execution-ready specification. This ensures every wave-based task declares file ownership up front and ties directly to the required project documentation and user story outcomes.
During sprint close, apply planning tools to propose targeted updates to living architecture docs, append sprint outcomes to project memory, and update the README. This keeps sprint documentation accurate and audit-friendly by tying doc proposals to shipped outcomes.
Non-overlapping file ownership rules prevent parallel execution conflicts by ensuring tasks in the same wave never touch the same files. Enforcing file ownership up front during task decomposition allows safe parallelization and keeps project documentation accurate.
bacocoGenerate developer-ready user stories with acceptance criteria from epics and architecture decisions.
jlawsExecute written plans in task batches with review checkpoints and verification.
BrennonTWilliamsAnalyze cross-issue dependencies from frontmatter fields to validate references and generate dependency graphs.
wilsonkichoiDecompose software specifications into atomic tasks with wave groupings and role assignments.
