plan-sprint
Skill0 starsChanged 7 months agoMITView on GitHub
スプリント全体の計画を /plan モードで立てる。sprint-planningの前段階。バックログを読んで全ストーリーの実装計画・並列化・コスト見積もりを一覧化する。
5 other projects use a version of this.
Adopted by
Most recently taken up by
- sebs/rewelotheir own version, first seen Nov 15, 2026
- jrjsmrtn/project-orchestration-skillstheir own version, first seen Nov 15, 2026
- salvo8519/fairmarktheir own version, first seen Nov 8, 2026
- link7373/agentic-pmotheir own version, first seen Aug 9, 2026
- trapajim/skillstheir own version, first seen May 11, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- jrjsmrtn/project-orchestration-skills★ 17same name
- sebs/rewelo★ 2same name
- trapajim/skills★ 2same name
- link7373/agentic-pmo★ 1same name
- salvo8519/fairmark★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- deploy-gcpSkill
- mobile-checkSkill
- plan-architectureSkill
- plan-featureSkill
- sprint-planningSkill
- sprint-reviewSkill
The file
Files
スプリント全体計画スキル(/plan フェーズ)
位置づけ
バックログ確定
→ /plan-sprint(スプリント全体計画) ← ここ
→ /sprint-planning(エージェント起動・worktree作成)
→ 各機能の /plan-feature
→ 実装実行内容(コードは書かない)
1. バックログ読み込み
docs/sprints/backlog.md を読んで今スプリントのストーリーを把握する。
2. スプリント計画書の生成
# Sprint-N 計画書
## ゴール
[1文で]
## ストーリー一覧と担当エージェント
| # | Story | 担当 | 依存 | 見積 | 並列可 |
|---|-------|------|------|------|--------|
| 1 | [name] | mobile+backend | なし | M | ✓ |
| 2 | [name] | infra | なし | S | ✓ |
| 3 | [name] | backend | Story-2完了後 | M | - |
## 実行ウェーブ(並列化計画)
Wave 1(並列):
- infra-agent: GCPリソース準備
- spec-agent: 仕様書作成(全ストーリー)
Wave 2(並列):
- mobile-agent: Story-1 UI実装
- backend-agent: Story-1,3 API実装
Wave 3(順次):
- test-agent: 全ストーリーテスト
- review-agent: レビュー
Wave 4:
- infra-agent: /deploy-gcp
## worktree構成
../feature-sprint-N-frontend ← mobile-agent
../feature-sprint-N-backend ← backend-agent
../feature-sprint-N-infra ← infra-agent
## トークンコスト見積もり
Wave1: Small(仕様・設計中心)
Wave2: Large(実装・並列)
Wave3: Medium(テスト・レビュー)
合計目安: Max プラン [N] タスク分
## リスク
[リスク1]: [対策]
[リスク2]: [対策]
## 前スプリントからの改善点(レトロより)
[改善点1]
[改善点2]3. 承認待ち
計画書提出後、人間の承認を得てから /sprint-planning を実行。
変更可能な項目:
- ストーリーの優先順位変更
- Wave の順序変更
- 特定ストーリーの次スプリント送り
4. アウトプット
docs/sprints/sprint-N/sprint-plan.md に保存
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

