Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/sprint-plan/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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.
[](https://agentmods.dev/skills/friedbotstudio/baseline/sprint-plan)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/sprint-plan"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/sprint-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/friedbotstudio/baseline/sprint-plan"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00093 | $0.00885 |
| Opus 5.5 | $0.00037 | $0.00354 |
| Sonnet 5.5 | $0.00019 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
sprint-plan 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-plan — author a sprint manifest with per-feature done-criteria
sprint-plan turns an MVP vision into a sprint manifest: a prioritized list of features, each carrying the done-criteria that make "done" mechanically checkable. The manifest is the input contract for sprint-oracle, which fails a sprint until every feature meets its criteria. This is Slice A of the mvp-sprint-parallel-cycles epic — the completeness half of the parallel-sprint goal (a sprint can be fast yet provably not partial).
What the manifest is
A JSON document (template-manifest.json is the shape). Each feature declares three done-criteria dimensions so completeness is a grep, not a judgment call:
done_record— a reference proving the feature is specified (a spec AC id, e.g.AC-012). Non-empty.edge_tests— names of tests covering error / empty / edge states. A non-empty array.wiring_test— the name of one integration test exercising the feature end-to-end.
{
"sprint": "<sprint name>",
"features": [
{
"id": "search",
"priority": "P0",
"done_record": "AC-012",
"edge_tests": ["search_empty_query", "search_unicode"],
"wiring_test": "search_end_to_end"
}
]
}
The test-tag convention (how sprint-oracle resolves the names)
A named test counts toward a feature only when the test file tags it. Immediately above the test('<name>', …) call, place:
// @sprint-feature:<feature-id> @kind:edge|wiring|happy
test('<name>', () => { /* … */ });
sprint-oracle builds a map of testName → {feature, kind} from these tags and resolves each manifest reference against it. A test tagged @kind:happy does not satisfy an edge or wiring requirement — that is the deliberate, mechanical line (no script can prove a test is semantically an edge case; the tag is the author's crisp claim, and the oracle verifies the claim resolves).
How to use
- Decompose the MVP vision into features. Decide priority (
P0/P1/…) per feature — scoping, not implementation. - For each feature, name its
done_record(the spec AC it traces to), theedge_testsit must carry, and itswiring_test. - Write the manifest (default location:
.claude/state/sprint/<sprint>/manifest.json, gitignored runtime state). - Validate the shape before handing it to the oracle:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 64 lines · 93 tokens per session scan A 011418d202fd
sprint-plan is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 93 tokens to every session and 885 once invoked, about $0.0004 per session on Opus 5.5. 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-30.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.