메뉴
Solo and team sprint pull-loop skills that drive an active sprint to completion by pulling entities from shark sprint next and delegating per-entity dispatch to the existing /run (or /run-agent-team) orchestration skill.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Query and manage project state and drive shark workflows — epics, features, tasks, bugs, change-cards, ideas. Use for ALL project state queries, task lifecycle, status transitions (status set / advance --outcome), claim/release/heartbeat leases, blocking/unblocking, notes/context/related-docs, status dashboards, analytics, creating/updating/deleting entities, and any command starting with "shark". Also the router for `/shark <verb>` and triggers the dispatch loop on `/run <key>`.
Multi-angle parallel code review. Six specialist subagents run in parallel (A: line-by-line bugs + production caller chains, B: removed behavior + SOLID, C: cross-file contracts + structural sibling check, D: reuse/complexity/idioms, E: tests design + counter-factual, F: standards crosswalk with citations), then a consolidator verifies and ranks findings into a PASS / PASS-with-triage / FAIL report with Blocker / Non-blocker / Nit triage. Triggered by /deep-review (aliases: /comprehensive-review, /pr-review). Flags: --fix (apply one-liner safe fixes), --comment (post as inline GitHub PR comments). Prompts live in references/angle-*.md and references/consolidator.md — readable on any platform even without the Workflow tool.
Authoritative source for all validation, code review, and quality assurance workflows. Provides consistent quality gates across all development phases.
Write the test first, watch it fail, write minimal code to pass (user) - when implementing any feature or bugfix, before writing implementation code
Orchestrate User Acceptance Testing for a feature — gather evidence, run Codex as the sole assessor, present a no-opinion report to the user, record results, route rejections, and triage non-blocking findings.
Quick-capture and classify a work item discovered during development, routing it to the correct entity type (task, feature, bug, tech-debt, change-card, idea, or note) under the right parent. Searches existing entities first to avoid duplication, proposes a classification, and confirms before creating. Use when you encounter work that needs to be recorded for later, the user says "/triage", or something should be tracked but its home is unclear. This is a capture-and-classify tool, NOT a create-and-elaborate tool.
| name | sprint-execution |
| display_name | Sprint Execution |
| description | Solo and team sprint pull-loop skills that drive an active sprint to completion by pulling entities from shark sprint next and delegating per-entity dispatch to the existing /run (or /run-agent-team) orchestration skill. |
A sprint-shaped harness around the existing orchestration skill. It knows how to loop over a sprint's work queue by calling shark sprint next --json, then hands each returned entity to /run (or /run-agent-team for team mode) for per-entity execution. It does not re-implement dispatch logic — that lives in the orchestration skill and shark's orchestrator_action field.
shark sprint next --json → entity key → /run {entity_key} → loop until empty
This skill covers two execution modes:
/run-sprint S### (solo) — sequential pull-loop for a single Claude session. Pulls one entity at a time, drives it to terminal status via /run, then pulls the next. Suitable for any sprint regardless of entity mix./run-sprint-team S### (team) — groups sprint entities by feature and bootstraps a Claude Code agent team per feature group via /run-agent-team. Features are dispatched serially (one team at a time, per the agent-teams primitive constraint). Standalone entities (bugs, change-cards, tech-debt without a feature parent) fall back to sequential /run dispatch.Both modes gate the sprint close operation on explicit user confirmation.
/run-sprint S### # Solo sequential execution
/run-sprint S### --agent=backend # Pull only backend-agent slice
/run-sprint S### --max-iterations=N # Cap loop at N (default 50)
/run-sprint S### --carryover=backlog # Carryover strategy if user confirms close
/run-sprint-team S### # Team execution, one feature at a time
/run-sprint-team S### --size=N # Override teammate count per feature team
/run-sprint-team S### --features=E##-F##,... # Restrict to specific features
See: workflows/run-sprint.md for the solo pull-loop workflow.
See: workflows/run-sprint-team.md for the team execution workflow.
/run: Sprint execution delegates per-entity dispatch to the existing orchestration skill rather than re-implementing it. This ensures orchestrator_action.instruction is always honored and workflow source-of-truth stays in shark.--max-iterations cap: Prevents runaway loops when shark sprint next returns the same entity repeatedly (e.g., an entity that bounced back to a non-terminal state). Default cap is 50.shark sprint close.--json or --field. Human-readable output is not a stable contract.--json or --fieldhead, tail, or grepshark sprint next --json returns the next entity object or an empty result; both cases are handled