plan-feature
Skill0 starsChanged 7 months agoMITView on GitHub
機能実装前に /plan モードで計画を立てる。コードを書く前に必ずこのスキルを実行し、人間の承認を得てから実装に移る。spec-agentの仕様書が確定した後に使う。
31 other projects use a version of this.
Adopted by
Most recently taken up by
- michagrandel/skillstheir own version, first seen Nov 16, 2026
- ViktorSoroka07/claude-delivery-skillstheir own version, first seen Nov 14, 2026
- seanmcgary/claude-skillstheir own version, first seen Nov 11, 2026
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- NemesLaszlo/Agent-Collectiontheir own version, first seen Nov 1, 2026
- olimstv/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use explore, review and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
OpenAISkillsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- Aurealibe/claude-config★ 68same name
- smartwhale8/claude-playbook★ 40same name
- uniffy-io/uniffy★ 24same name
- nowsprinting/unity-coding-skills★ 20same name
- asta-nguyen/kamehadb★ 14same name
- Karthick-Ramachandran/persist-os★ 9same name
- MooseDesign1/DDD-DesignDrivenDevelopment★ 9same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- iopsystems/skills-mcp★ 6same name
- lautioliver/barrilete-kit★ 6same name
21 more not listed
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-sprintSkill
- sprint-planningSkill
- sprint-reviewSkill
The file
Files
機能計画スキル(/plan フェーズ)
位置づけ
spec-agent(仕様確定)
→ /plan-feature(計画・承認) ← ここ
→ 実装エージェント(コード作成)実行方法
Claude Code で /plan を入力するか、このスキルを呼ぶ。
コードは一切書かない。計画だけを出力する。
計画書のフォーマット(TDD ファースト)
1. 対象ストーリーの確認
Story: [story名]
仕様書: docs/sprints/sprint-N/specs/[story].md
スプリントゴールとの関係: [一言]2. テスト計画(最優先・実装より先に書く)
このプロジェクトは TDD が必須。実装ファイル一覧の前に、書くべきテストを列挙する。
バックエンドテスト(backend/tests/):
test_[name].py::test_[behavior] → 検証内容: [...]
test_[name].py::test_[edge case] → 検証内容: [...]
フロントエンドテスト(同居 *.test.ts):
src/lib/[path]/[name].test.ts::it('...') → 検証内容: [...]
E2E(Playwright):
[シナリオ]: [操作 → 期待結果]
/mobile-check 確認ポイント:
- 375px レイアウト
- LCP / CLS
- タッチターゲット 44px
- PWA manifest
このテスト群が **書ける = 実装の契約が確定している** という意味。書けない箇所は仕様の曖昧さなので spec-agent に差し戻し。3. 影響範囲の分析
変更するファイル:
frontend/src/routes/[path]/+page.svelte → [変更内容]
backend/routers/[name].py → [変更内容]
backend/models/[name].py → [変更内容]
新規作成するファイル:
[ファイルパス] → [目的]
変更しないファイル:
[理由と根拠]4. API契約(フロント↔バック合意点)
エンドポイント: POST /api/v1/[resource]
リクエスト: { field: type }
レスポンス: { field: type }
エラーケース:
400: [条件]
401: 未認証
404: [条件]※ この契約がそのままセクション 2 のテストの assertion になる。
5. Firestore データ設計
コレクション: [name]
ドキュメント構造:
{
uid: string,
[field]: type,
created_at: Timestamp,
updated_at: Timestamp
}
セキュリティルール変更: 要 / 不要6. スマホ対応計画
レイアウト: [375px でのUI方針]
タッチ操作: [必要なジェスチャー]
オフライン: [対応方針]
パフォーマンス懸念: [LCP・CLSへの影響]7. 実装順序(TDD ベース)
Step 0: テストファイル作成(セクション 2 の内容) ← Red を先に作る
Step 1: infra-agent → [GCPリソース準備]
Step 2: backend-agent → 失敗テスト確認 → 最小実装 → Green
Step 3: mobile-agent → 失敗テスト確認 → 最小実装 → Green(Step2 と並列可能)
Step 4: 全エージェント → リファクタ(テスト緑のまま)
Step 5: review-agent → レビュー(コミット履歴で TDD 順序を確認)8. リスクと対策
リスク: [発生しうる問題]
対策: [回避・軽減策]
代替案: [計画が崩れた場合の選択肢]9. 見積もり
infra-agent: [時間]
backend-agent: [時間](うちテスト記述: [時間])
mobile-agent: [時間](うちテスト記述: [時間])
合計: [時間]
コストトークン見積もり: [Small/Medium/Large]承認プロセス
計画書を出力後、人間(PO/のぶさん)の承認を待つ。 承認なしに実装エージェントを起動しない。
承認コメント例:
- 「計画承認。実装開始」→ orchestratorがエージェントを起動
- 「Step 3を先に」→ 順序を修正して再提出
- 「Firestore設計を変更」→ データ設計を修正して再提出
アウトプット
docs/sprints/sprint-N/plans/[story]-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.

