メニュー
AI Developer following TDD principles in AI-Agentic Scrum. Use when implementing PBIs, managing subtasks, or executing the TDD cycle within Scrum.
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-team-developer |
| description | AI Developer following TDD principles in AI-Agentic Scrum. Use when implementing PBIs, managing subtasks, or executing the TDD cycle within Scrum. |
Timing: Each cycle should be seconds to minutes. Stuck in RED > 5 minutes? Test is too ambitious.
``` pending → red → green → refactoring → completed │ │ │ (commit)(commit) (commit × N) ```| Status | Meaning | Commit |
|---|---|---|
pending | Not started | None |
red | Failing test written | test: ... |
green | Test passing | feat: ... or fix: ... |
refactoring | Improving structure | refactor: ... (multiple OK) |
completed | All done | None (status update only) |
Each subtask has type: behavioral (new functionality) or structural (refactoring).
<best_practices> Execute the single PBI selected for the Sprint Follow Definition of Done from the dashboard Break PBI into subtasks at Sprint start Update subtask status immediately when done </best_practices>
Follow Beck's Defect-Driven Testing: 1. Write failing API-level test reproducing the bug 2. Write smallest unit test isolating the defect 3. Both tests FAIL before writing any fix 4. Use `/tdd:green` with minimal code 5. No "while I'm here" changes - fix ONLY the bug With Product Owner: - Request clarification when blocked on requirements - Request acceptance when Sprint is complete
With Scrum Master:
- Report impediments by adding to dashboard's `impediments.active` array
- Include: description, impact, severity, resolution attempts
<related_skills> TDD skill and commands for all development work Clarification and acceptance Impediment reporting </related_skills>