Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/community/sprint/skills/sprint-workflow

sprint-workflow

Verified

Execute this skill should be used when the user asks about "how sprints work", "sprint phases", "iteration workflow", "convergent development", "sprint lifecycle", "when to use sprints", or wants to understand the sprint execution model and its convergent diffusion approach. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

FileKindSize
SKILL.mdskill md5.5 KB
references/errors.mdmarkdown319 B
references/examples.mdmarkdown9.0 KB
references/sprint-phases.mdmarkdown1.6 KB

references/sprint-phases.md

View on GitHub
# Sprint Phases

## Sprint Phases

A sprint executes through 6 distinct phases:

### Phase 0: Load Specifications

Parse the sprint directory and prepare context:

- Locate sprint directory (`.claude/sprint/[N]/`)
- Read `specs.md` for user requirements
- Read `status.md` if resuming
- Detect project type for framework-specific agents

### Phase 1: Architectural Planning

The project-architect agent analyzes requirements:

- Read existing `project-map.md` for architecture context
- Read `project-goals.md` for business objectives
- Create specification files (`api-contract.md`, `backend-specs.md`, etc.)
- Return SPAWN REQUEST for implementation agents

### Phase 2: Implementation

Spawn implementation agents in parallel:

- `python-dev` for Python/FastAPI backend
- `nextjs-dev` for Next.js frontend
- `cicd-agent` for CI/CD pipelines
- `allpurpose-agent` for any other technology
- Collect structured reports from each agent

### Phase 3: Testing

Execute testing agents:

- `qa-test-agent` runs first (API and unit tests)
- `ui-test-agent` runs after (browser-based E2E tests)
- Framework-specific diagnostics agents run in parallel with UI tests
- Collect test reports

### Phase 4: Review & Iteration

Architect reviews all reports:

- Analyze conformity status
- Update specifications (remove completed, add fixes)
- Update `status.md` with current state
- Decide: more implementation, more testing, or finalize

### Phase 5: Finalization

Sprint completion:

- Final `status.md` summary
- All specs in consistent state
- **Clean up manual-test-report.md** (no longer relevant)
- Signal FINALIZE to orchestrator
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall