メニュー
Tiered cap rule for mission scope on fleet-generator — Tier 1 primitive-touching ≤3 edits, Tier 2 UI-bounded ≤6 edits, Tier 3 net-new no cap, plus atomic exception.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/bob-codedaptive/fleet-generator --skill mission-scopingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Mandatory pre-commit checklist for Woodstock streams — scope check, identity check, test verification, anti-pattern detection, and the type(scope): description commit-message format.
Standard subagent flow for fleet-generator — when Woodstock spawns Snoopy for pre-flight, when to spawn Garfield for review, and when specialist reviewers (Dogbert, Cathy, Odie) get pulled in. Always-active doctrine.
Per-agent git commit identity for fleet-generator. Every agent signs commits so the human can scan git log and tell who did what.
| name | mission-scoping |
| description | Tiered cap rule for mission scope on fleet-generator — Tier 1 primitive-touching ≤3 edits, Tier 2 UI-bounded ≤6 edits, Tier 3 net-new no cap, plus atomic exception. |
| when_to_use | Authoring a mission. Deciding whether a mission should be split. Pre-flight scanner verifying scope. Worker flagging RESCOPE_REQUIRED mid-mission. Trigger phrases: mission scoping, primitive-touching, Tier 1, Tier 2, Tier 3, ≤3 edits, UI-bounded, net-new, atomic exception, RESCOPE_REQUIRED, split the mission, cap. |
| status | active |
| tags | ["skill"] |
| updated | 2026-05-07T00:00:00.000Z |
A flat cap ("≤ 3 files") works for primitive-touching missions and over-splits everything else. The tiered model keeps discipline where it matters and removes friction where it doesn't.
When a mission touches any primitive (a type or symbol whose blast radius spans the codebase), the cap is strict: ≤ 3 edits to existing files.
For fleet-generator, primitives include core domain types, schema fields, public API surfaces, and shared utilities used in many call sites. If a mission edits 3 files and one defines a primitive, the mission is at the cap. A fourth file edit triggers RESCOPE_REQUIRED.
When a mission is bounded by a single UI component cluster (a screen, modal, or named feature) and touches no primitive, the cap is 6 files within the bounding component.
The mission must name the bounding component in its scope:
SettingsScreen and its tests"PaymentModal and its view-model"Edits outside the named component count against Tier 1.
When a mission only adds new files and edits no existing file, there is no cap. Adding 12 new files for a feature is fine.
The mission must explicitly state "all-new files, no edits to existing code" and Garfield verifies post-flight.
When a logical change cannot be split without producing an intermediate broken state on the integration branch, the cap doesn't apply. The mission must include an atomic justification naming why splitting would break the build.
Examples that warrant atomic exception:
Examples that do NOT:
When the orchestrator authors a mission and the pre-flight scanner checks it, the gate is:
If none, split the mission before admission.
If the worker discovers mid-mission that the actual blast radius exceeds the scoped tier:
See references/examples.md for four worked cases.