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.
npx agentmods add rules/hundia/autospec/plan-sprintgit clone --depth 1 https://github.com/Hundia/autospecWrote 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/rules/hundia/autospec/plan-sprint)<a href="https://agentmods.dev/rules/hundia/autospec/plan-sprint"><img src="https://agentmods.dev/badge/rules/hundia/autospec/plan-sprint.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00910 |
| Opus 5 | $0.00000 | $0.00455 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
plan-sprint 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 today.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Sprint
Plan a sprint using multi-expert analysis and PM synthesis. This produces a prioritized, dependency-aware sprint plan written to specs/backlog.md.
Phase 1: Goal Analysis & Expert Selection
- Read
specs/backlog.mdto understand the current state - Read
specs/01-project-overview.mdfor project goals and constraints - Identify the sprint goal (what should be accomplished)
- Select which experts to activate based on the goal
Expert Activation Criteria
| Expert | Activate When |
|---|---|
| Architect | New subsystem, major refactor, integration work |
| UX/UI | User-facing features, viewer changes, new workflows |
| Database | Schema changes, data migration, query optimization |
| Human Experience | Onboarding flows, error messages, documentation UX |
| Security | Auth changes, input handling, API exposure |
| Performance | Load concerns, bundle size, query efficiency |
Activate 2-4 experts per sprint. Always include Architect for structural changes.
Phase 2: Expert Analysis
Each activated expert provides:
- Assessment: What does this sprint goal mean for their domain?
- Risks: What could go wrong?
- Recommendations: Specific tickets or approaches
- Dependencies: What must happen first?
- Effort estimate: T-shirt size (S/M/L/XL) per recommendation
Expert Output Format
### Expert: [Role]
**Assessment**: [1-2 sentences]
**Risks**: [bulleted list]
**Recommendations**:
- [ticket idea] (Size: M, Depends on: none)
- [ticket idea] (Size: L, Depends on: above)
**Dependencies**: [cross-expert dependencies]
Phase 3: PM-A Draft
The first PM synthesizes expert input into a draft sprint plan:
- Collect all expert recommendations
- Resolve conflicting advice (prefer Architect for structure, UX for user-facing)
- Order tickets by dependency and priority
- Assign ticket numbers (X.1, X.2, etc.)
- Write the draft sprint section
Draft Format
## Sprint X — [Sprint Goal]
- 🔲 **X.1** — [Description] (Size: S)
- 🔲 **X.2** — [Description] (Size: M, depends on X.1)
- 🔲 **X.3** — [Description] (Size: L)
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.
- today First seen · 119 lines · 0 tokens per session scan A 6f6cfad7f3b1
plan-sprint is a cursor rule 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 910 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-09-03.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
development-workflow
AAMAD modular development workflow for context-aware agent coordination.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.