sprint-orchestrator
Skill19 starsChanged 12 months agoMITView on GitHub
Coordinates multi-task sprint execution, manages research workflow, and ensures quality. Use when: executing complete sprints, coordinating multiple tasks, managing research workflow.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read sprint configuration from config/sprint-config.yml
- Very specific: line 16
Create sprint directory structure in temp/sprint-XX/
- Distinctive: line 19
Ensure cross-references between tasks
- Distinctive: line 23
Initialize Sprint: Create directories, validate config
- Distinctive: line 27
Validate: Run quality checks before marking sprint complete
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sprint Orchestrator Skill
Role
Coordinate sprint execution across all 6 tasks, manage workflow, and ensure quality standards are met.
Responsibilities
- Read sprint configuration from
config/sprint-config.yml - Create sprint directory structure in
temp/sprint-XX/ - Invoke specialist skills (technical-researcher, market-analyst, etc.) for each task
- Monitor progress and quality metrics
- Ensure cross-references between tasks
- Coordinate final synthesis
Workflow
- Initialize Sprint: Create directories, validate config
- Execute Tasks 01-05: Invoke specialist skills in parallel where possible
- Monitor Quality: Track file count, citation coverage, completeness
- Synthesize: Invoke report-synthesizer for Task 06
- Validate: Run quality checks before marking sprint complete
Output
- Sprint summary in
temp/sprint-XX/README.md - Progress tracking with TodoWrite
- Quality metrics and validation results
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lipefur/sprint-orchestrator★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- comparative-analyzerSkill
- compliance-analystSkill
- market-analystSkill
- opportunity-discoverySkill
- opportunity-scorerSkill
- quality-validatorSkill
- report-generatorSkill
- report-synthesizerSkill
- research-synthesizerSkill
- roadmap-plannerSkill
- solution-architectSkill
- sprint-executorSkill
- sprint-progress-trackerSkill
- technical-researcherSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

