Skip to content

hoavdc/CodexKit / skills/codexkit-sprint-planning-assistant

codexkit-sprint-planning-assistant

Verified

Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.

FileKindSize
SKILL.mdskill md3.5 KB
agents/openai.yamlconfig170 B
examples/common-mistakes.mdmarkdown810 B
examples/good-output.mdmarkdown794 B
verification/checklist.mdmarkdown1.3 KB

examples/good-output.md

View on GitHub
# Good Output Example — Sprint Planning Assistant

> This example demonstrates what well-executed sprint planning assistant output looks like.

## Scenario

2-week sprint plan for a 5-person engineering team

## Why It Works

1. Capacity: '5 engineers × 10 days = 50 days. PTO: 3 days. On-call: 2 days. Net: 45 days (36 SP at 0.8 velocity)'
2. Sprint goal: 'Ship user profile redesign and reduce P1 bug count by 50%'
3. Priority stack: 'Stories 1-5 (must), 6-8 (should), 9-10 (stretch)'
4. Risks: 'Story #3 depends on API team — standup sync on Tuesday to confirm.'

## Key Patterns to Replicate

- Stories ordered by priority, not by who picks them first
- Capacity is math, not vibes: show the calculation
- Sprint goal can pass a newspaper test: someone outside the team understands it
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall