skills.rest
ComputerConnection
ComputerConnectionCOMMUNITY
Explore all skills by this author →
GitHub

sprint-planner

Analyze repository source code and git history to generate an audit, roadmap, and sprint plan.

Updated Mar 31, 2026
Search Tags:#sprint planning#product strategy#code audit#stakeholder alignment#pm gates#roadmap design
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill sprint-planner-computerconnection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/sprint-planner
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill sprint-planner-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Sprint Planner orchestrates a reality-grounded three-stage product strategy pipeline that starts from reading actual code and progresses to a concrete sprint plan.

Core Features & Use Cases

  • Three-stage pipeline: Audit → Roadmap → Sprint Plan, with PM decision gates between stages to ensure intentional progress.
  • Grounded planning: Cross-references source code and git history to reveal real work state and inform prioritization.
  • Deliverables and traceability: Outputs include annotated deliverables with exact file paths and dependency relations, ready for engineering execution.

Quick Start

Run the sprint-planner against your codebase to generate the audit deliverable.

Frequently Asked Questions about sprint-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint plan from a code audit?▼

You can generate a sprint plan from a code audit by running a three-stage pipeline that reads source code and git history, producing an audit, roadmap, and sprint plan with PM gates and exact file paths.

What is code-grounded sprint planning?▼

Code-grounded sprint planning cross-references actual source code and git history to reveal real work state, ensuring product roadmaps and sprint plans are anchored in implementation details rather than abstract estimates.

Can I use repository git history to inform product roadmap design?▼

Yes, you can use repository git history to inform product roadmap design by analyzing commit history and code structure to reveal the actual work state, which then grounds the roadmap and sprint plan deliverables.

How do PM decision gates work during sprint planning?▼

PM decision gates act as checkpoints between the audit, roadmap, and sprint plan stages, ensuring intentional progress and stakeholder alignment before advancing to the next deliverable.

Does this sprint planning approach require specific dependencies or components?▼

No, this sprint planning approach requires no specific dependencies or components, allowing you to directly analyze your repository source code to generate actionable deliverables for engineering teams.

What is the best way to align engineering execution with product strategy?▼

The best way to align engineering execution with product strategy is to use a pipeline that cross-references source code and git history, producing a sprint plan with exact file paths, dependency relations, and PM gate criteria.

Related Skills

Explore More Product & Management Skills→
axel-kaliffaxel-kaliff

rethink

Analyze git history and code to identify design flaws and scope drift.

Community
Advanced
kanitmann01kanitmann01

project-manager

Plan and track team tasks with owners and acceptance criteria.

Community
Intermediate
tonombtonomb

wayfinder

Decompose high-level objectives into dependency-aware issue tracker tickets.

Community
Advanced
petekppetekp
5

agent-changelog

Compile an agent-focused changelog by cross-referencing git history, plans, and documentation.

Community
Advanced