agentsclimarketplace

Sprint planning

Skill shinzoxD/knackbox/skills/productivity/sprint-planning

Run sprint or iteration planning with capacity, goals, and clear commit scope. Use whenever the user asks for sprint planning help, iteration planning, backlog prioritization for a sprint, or capacity-based planning for a team.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill sprint-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, 259 tokens by cl100k_base, as published. Nobody here has run it

Sprint Planning

Planning commits the team to a realistic slice of value. Protect focus; do not stuff the sprint with hope.

Workflow

  1. Sprint goal (one sentence outcome).
  2. Capacity: people, PTO, on-call, meetings; use historical throughput.
  3. Candidate backlog ordered by priority/risk.
  4. Break work to fit; expose dependencies.
  5. Commit vs stretch clearly.
  6. Risks and unplanned buffer for support/interrupt teams.
  7. Definition of done and demo expectation.

Output format

## Sprint plan — <dates>
**Goal:** …

### Capacity
…

### Committed
| Item | Why | Estimate |

### Stretch
…

### Dependencies / risks
…

### Ceremonies
…

Rules

  1. Goal over story-point theater.
  2. Do not plan 100% utilization.
  3. Carryover needs explicit cause and cut decisions.
  4. Spike/research items need timeboxes and outputs.
  5. Interrupt-driven teams need thicker buffer.
  6. Refuse fantasy deadlines without capacity math.

Edge cases

  • First sprint for new team: smaller commit, more discovery.
  • Hard deadline: cut scope transparently.
  • Multi-team: integration milestones explicit.

What ships with it: 1 file

1.2 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.