菜单
Mode-aware sprint scoping skill that walks an orchestrator or human through planning a sprint by reading shark sprint plan and readiness data, proposing entity assignments, and confirming changes. Never starts the sprint — starting is an explicit user action via /shark run-sprint.
用 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 Planning |
| description | Mode-aware sprint scoping skill that walks an orchestrator or human through planning a sprint by reading shark sprint plan and readiness data, proposing entity assignments, and confirming changes. Never starts the sprint — starting is an explicit user action via /shark run-sprint. |
A mode-aware sprint scoping harness. It reads shark sprint plan once at the start, surfaces backlog entities grouped by feature and agent type, and walks through assignment confirmation — either item-by-item (interactive mode) or with a single greedy-fill proposal (auto mode). When done, it reports the readiness-score delta and suggests /shark run-sprint as the next step. It does NOT call shark sprint start.
shark sprint plan {S###} --json → surface backlog → confirm assignments → shark sprint readiness {S###} --json → report delta
It does NOT decide which sprint strategy to use. It reads capacity and readiness from shark, proposes based on that data, and requires explicit user confirmation before any shark sprint add call.
/shark plan-sprint S### # Interactive mode (default)
/shark plan-sprint S### --mode=auto # Greedy-fill with single confirmation
/shark plan-sprint S### --mode=interactive # Explicit interactive (same as default)
/shark plan-sprint S### --max-add=N # Limit total entities added this session
Read workflows/plan-sprint.md to get the full step-by-step workflow procedure.
shark sprint add only after explicit per-item or per-group confirmation.shark sprint add for each selected entity.--json or --fieldhead, tail, or grep