メニュー
Guide Sprint Planning in AI-Agentic Scrum. Use when selecting PBI, defining Sprint Goal, or breaking into subtasks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
MyLifeのスクラップ要約を作成する。ユーザーが「スクラップ要約」「前日分のスクラップを要約」「Clippingsをデイリーノートに追記」「~/MyLife/Clippings の記事をまとめて」などと依頼したときに使う。Asia/Tokyo基準で対象日を決め、~/MyLife/Clippings/ のYYYYMMDD始まりのファイルからタイトル・URL・本文を抽出し、~/MyLife/pages/YYYY_MM_DD.md の `## 要約` セクションを新規作成または置換する。
Collect analytics from YouTube Studio in Microsoft Edge and save them as a CSV with a fixed schema. Use when Codex is asked to open YouTube Studio, switch to a specific managed channel if needed, read the past 28 days of per-video metrics such as views, average view duration, likes, comments, saves, and impressions, and save the result as a CSV file.
Guide behavior-preserving code refactoring with a language-agnostic core, Fowler-aligned catalog references, and team-specific extension patterns. Use during the TDD REFACTOR phase, when code smells are detected, when preparing for later behavior changes, or when discussing structural improvements.
Orchestrate full implementation lifecycle with sub-agent team delegation through 6 strict phases: Tidy First -> Implement -> TDD Red -> Green -> Refactor -> Tidy After. The leader gives instructions only; sub-agents do all research and coding. Use when user explicitly invokes /implements or says "実装して", "これを実装", "implement this". NOT for quick fixes, single-file edits, or tasks that don't warrant the full 6-phase ceremony.
Boris Tane's structured 3-phase workflow for non-trivial tasks: Research → Plan → Todo → Implement. Use when starting a new feature, refactoring, bug investigation, or any task where you want to plan deeply before coding. Creates research.md, plan.md, and todo.md as shared artifacts for iterative refinement. DO NOT write code until the plan is explicitly approved. Trigger when user says "研究して", "計画を立てて", "research and plan", "plan before coding", or starts a complex task that benefits from upfront analysis.
Use when user says "wrap up", "close session", "end session", "wrap things up", "close out this task", or invokes /wrap-up — runs end-of-session checklist for shipping, memory, and self-improvement
| name | scrum-event-sprint-planning |
| description | Guide Sprint Planning in AI-Agentic Scrum. Use when selecting PBI, defining Sprint Goal, or breaking into subtasks. |
Before selecting, verify Definition of Ready:
- Clear user story with role, action, benefit
- Acceptance criteria specific and testable
- Dependencies identified and resolved
- No blocking questions remaining
- Has executable verification commands
Characteristics:
- Evaluable: Can clearly determine if achieved
- Stakeholder-Understandable: Meaningful outside the team
- Outcome-Focused: Value delivered, not tasks completed
- Fixed: Does not change during Sprint
Working backwards - ask:
- "What do we want to demonstrate at Sprint Review?"
- "What would make stakeholders excited?"
- "What can we show as a working increment?"
Subtask format in `scrum.ts`:
```yaml
subtasks:
- test: "What behavior to verify (RED phase)"
implementation: "What to build (GREEN phase)"
type: behavioral # behavioral | structural
status: pending # pending | red | green | refactoring | completed
commits: []
notes: []
```
Subtask types:
- `behavioral`: New functionality (RED → GREEN → REFACTOR)
- `structural`: Refactoring only (skips RED/GREEN, goes to refactoring)
<best_practices>
Keep subtasks small (completable in one TDD cycle)
Order by logical dependency
Each subtask independently testable
Update status immediately when completing
Mark type: behavioral or structural
</best_practices>
<anti_patterns> "Complete all Sprint Backlog items" (not a goal) "Finish Stories A, B, and C" (output-focused) Goals only developers understand </anti_patterns>
<related_skills> Sprint Goal input, Product Backlog prioritization Task breakdown, technical feasibility Facilitation, impediment removal </related_skills>
A successful Sprint Planning produces shared understanding of WHY the Sprint matters, WHAT will be delivered, and HOW the team will achieve the Sprint Goal.