sprint
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: sprint
description: Advance to next sprint or create sprint from description Create a new sprint or advance to the n…
category: data
runtime: no special runtime
---
# sprint output preview
## PART A: Task fit
- Use case: Advance to next sprint or create sprint from description Create a new sprint or advance to the next one. subject: "[verb] [specific deliverable]", description: "## What\n[Exactly what to build]\n\n## Acceptance Criteria\n- [ ] [Testable outcome]\n- [ ] Build passes\n- [ ] No type errors\n\n## Files\n- src/path/file.ts - [what to change]", runs entirely lo….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Usage / Creating from Description / Advancing (sprint next)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Advance to next sprint or create sprint from description Create a new sprint or advance to the next one. subject: "[verb] [specific deliverable]", description: "## What\n[Exactly what to build]\n\n## Acceptance Criteria\n- [ ] [Testable outcome]\n- [ ] Build passes\n- [ ] No type errors\n\n## Files\n- src/path/file.ts - [what to change]", runs entirely lo…”.
- **02** When the source has headings, the agent prioritizes “Usage / Creating from Description / Advancing (sprint next)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Usage / Creating from Description / Advancing (sprint next)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: sprint
description: Advance to next sprint or create sprint from description Create a new sprint or advance to the n…
category: data
source: majiayu000/claude-skill-registry
---
# sprint
## When to use
- Advance to next sprint or create sprint from description Create a new sprint or advance to the next one. subject: "[ve…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Usage / Creating from Description / Advancing (sprint next)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "sprint" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Usage / Creating from Description / Advancing (sprint next)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Sprint
Create a new sprint or advance to the next one.
Usage
sprint [description]- Create new sprint from feature descriptionsprint next- Advance to next sprint from roadmap
Creating from Description
- Parse $ARGUMENTS as feature description
- Generate epic prefix from description
- Create/update project-meta.json with new sprint
- Generate 10-20 stories via TaskCreate with full metadata (see quality skill for schema):
TaskCreate({ subject: "[verb] [specific deliverable]", description: "## What\n[Exactly what to build]\n\n## Acceptance Criteria\n- [ ] [Testable outcome]\n- [ ] Build passes\n- [ ] No type errors\n\n## Files\n- `src/path/file.ts` - [what to change]", activeForm: "[Building|Adding] [short desc]", metadata: { sid: "[PREFIX]-[NNN]", sprint: currentSprint, epic: "[epic name]", priority: [1-3], category: "[auth|ui|perf|security|qa|infra]", type: "feature", passes: null, verified: null } })- Include file paths, patterns to follow
- Set dependencies between stories
- Report sprint summary
Advancing (sprint next)
- Read project-meta.json
- Mark current sprint as "done"
- Find next unscheduled roadmap epic(s)
- Create new sprint with stories from those epics
- Update project-meta.json
Rules
- HARD CAP: 20 stories per sprint
- Stories must be detailed enough to implement without guessing
- Every story must be testable
- If user asks to "expand", explain roadmap and offer
sprint next
Decide Fit First
Design Intent
How To Use It
Boundaries And Review