sprint-reviewer

To review a sprint plan for dependency and sequencing issues, you can use a skill that validates dependencies, identifies phantom dependencies, and suggests parallelism opportunities based on the sprint tag.

Sprint plan fragmentation analysis identifies over-fragmentation and under-fragmentation in task cards. You need it to ensure your sprint plan adheres to best practices and standards before execution.

You can check adherence to the three laws of card design by running an adversarial review on your sprint plan, which provides a critical assessment of clarity, focus, and structural standards.

No, you do not need external dependencies to analyze sprint planning quality. The sprint review process requires no external dependencies and utilizes gitban MCP tools for card interaction and analysis.

The best way to validate task sequencing and parallelism is to run a dependency and sequencing analysis on your sprint plan, which generates a detailed report with findings and a final verdict on plan quality.

Yes, you can generate a quality report for your sprint plan before execution by running a review command, which outputs findings, recommendations, and a final verdict on the plan's quality.