create-sprint-docs

create-sprint-docs is a command for Claude Code from Hundia/autospec. It costs 0 tokens per session (1,052 once invoked), scanned A, original, MIT.

A command that turns a finished sprint—a planned batch of development work—into a folder of documentation. It checks the backlog, gathers changed files and test results, and creates three Markdown documents.

In plain words
What is it for?
Use it after a sprint to record its goal, user-facing changes, technical changes, configuration updates, and test results.
Why use it?
It removes the need to assemble sprint notes by hand and helps catch work that is not actually complete before documenting it.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/hundia/autospec/create-sprint-docs
Clone the repo
git clone --depth 1 https://github.com/Hundia/autospec

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-sprint-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/hundia/autospec/create-sprint-docs.svg)](https://agentmods.dev/commands/hundia/autospec/create-sprint-docs)
Your own site
<a href="https://agentmods.dev/commands/hundia/autospec/create-sprint-docs"><img src="https://agentmods.dev/badge/commands/hundia/autospec/create-sprint-docs.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,052 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01052
Opus 5 $0.00000 $0.00526
Sonnet 5 $0.00000 $0.00210
Haiku 4.5 $0.00000 $0.00105

Measured 3d ago against content hash 59cfee460395, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-sprint-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/create-sprint-docs.md · 204 lines

How it starts

The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Sprint Docs

Generate documentation for completed sprints.

Usage

/create-sprint-docs [sprint_number]

Example: /create-sprint-docs 4

Instructions

When this command is invoked:

  1. Verify sprint is complete:

    • Read specs/backlog.md
    • Ensure all tickets are ✅ Done
    • If not complete, warn user
  2. Gather sprint data:

    • Sprint name and goal
    • All tickets with final status
    • Files changed (via git)
    • Test results
  3. Create sprint folder:

    • Create sprints/sprint-XX-[name]/
  4. Generate three documents:

Document 1: summary.md

# Sprint [X]: [Name]

**Date:** [Completion Date]
**Status:** ✅ Complete
**QA:** [X/X Tests Passed](./qa-results.md)

## Goal
[Sprint goal from backlog]

## What's New (User-Facing)
- [Feature 1]: [Brief description]
- [Feature 2]: [Brief description]

## Technical Summary

### Backend Changes
| File | Change |
|------|--------|
| [path] | [description] |

### Frontend Changes
| File | Change |
|------|--------|
| [path] | [description] |

### Database Changes
| Migration | Description |
|-----------|-------------|
| [number] | [description] |

## Configuration Changes
- [New env var or config, or "None"]

## Breaking Changes
- [Description, or "None"]

## Dependencies Added
- [Package: version, or "None"]

## Tickets Completed
| # | Ticket | Owner | Model |
|---|--------|-------|-------|
| X.1 | [Description] | [Role] | [Model] |

## Notes
[Any important notes for future reference]

Document 2: qa-results.md

# Sprint [X]: QA Test Results

**Date:** [Date]
**Tester:** [Automated/Name]
**Result:** ✅ [X/X] Tests Passed

## Test Summary
| Category | Passed | Failed | Skipped |
|----------|--------|--------|---------|
| Unit | X | 0 | 0 |
| Integration | X | 0 | 0 |
| E2E | X | 0 | 0 |
| **Total** | **X** | **0** | **0** |

## Test Results by Ticket

### Ticket X.1: [Description]
- ✅ Unit tests (X/X)
- ✅ Integration tests (X/X)

### Ticket X.2: [Description]
- ✅ Unit tests (X/X)
- ✅ Component tests (X/X)

## Test Environment
| Component | Version |
|-----------|---------|
| Node.js | X.X.X |
| Database | PostgreSQL X.X |
| OS | [Platform] |

## Coverage Report
| Metric | Value | Target |
|--------|-------|--------|
| Lines | X% | 70% |
| Functions | X% | 70% |
| Branches | X% | 60% |

## Issues Found & Resolved
| Issue | Severity | Ticket | Resolution |
|-------|----------|--------|------------|
| [Description] | [H/M/L] | B.X | [How fixed] |

## Known Limitations
- [Any known issues not blocking release]

Read the full file on GitHub · 204 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 204 lines · 0 tokens per session scan A 59cfee460395

Subscribe to this mod's changes

create-sprint-docs is a command published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,052 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.