Menu
Use after spec is drafted to plan implementation; produces decisions, tasks, verification-gate, and implementer handoff. Do NOT write code, do NOT lock decisions on operator's behalf, do NOT run before spec exists.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | implementation-planning |
| description | Use after spec is drafted to plan implementation; produces decisions, tasks, verification-gate, and implementer handoff. Do NOT write code, do NOT lock decisions on operator's behalf, do NOT run before spec exists. |
| source_inspiration | conceptual-only |
| license_status | clean-room-original |
| fusebase_flow_version | 2.1 |
| risk_level | medium |
| invocation | automatic |
| expected_outputs | ["docs/specs/<slug>/decisions.md","docs/specs/<slug>/tasks.md","docs/specs/<slug>/verification-gate.md","docs/tmp/handoff/<YYYY-MM-DD>-<slug>-implement.md"] |
| related_workflows | ["eight-phase-flow.md","greenlight-implement.md","architect-escalation.md"] |
| hook_dependencies | ["none"] |
Convert a drafted spec into the artifacts an AI Developer session needs to execute: a letter-decision matrix, a numbered task chain, a verification-gate contract, and a saved handoff prompt.
Plan or Decisions (per FLOW_RULES state announcement)docs/specs/<slug>/spec.md with status DRAFT and clarify questions resolvedDRAFT with unresolved clarify questions (re-invoke requirements-specification instead)decisions.md Lock status: LOCKED) and decisions/tasks already exist (use code-review or validation-and-qa instead)Before drafting any planning artifact, apply the tier from flow-skills/documentation-budget/SKILL.md (don't duplicate it). Create each artifact ONLY when its trigger holds:
| Artifact | Create only when |
|---|---|
decisions.md | a real decision exists — alternatives with rejection reasons or a locked tradeoff to preserve. No real decision → omit the file (do not write single-option "decisions") and record the literal line no real decisions in spec.md's Clarify summary — greenlight-implement + required-artifacts.yml: optional_when consume it. |
tasks.md | Tier 3/4 (multi-file Full-lane work). Reference ACs by pointer (spec.md AC1..ACn); do not reprint them. |
verification-gate.md | Full lane or policies/required-artifacts.yml / policies/gate-contracts.yml requires it for this tier. |
| implement handoff | a fresh AI Developer session will execute the chain. Point to canonical spec/decisions/tasks; do NOT reprint them. |
Fail-safe: when unsure, choose the higher tier. Never weaken a safety artifact required by policy to "save docs". (Lightweight-eligible work should not reach this skill — it takes the change-note path in requirements-specification.)
| Input | Where it lives | If missing |
|---|---|---|
| Spec | docs/specs/<slug>/spec.md (status DRAFT) | Re-invoke requirements-specification |
| Acceptance criteria | numbered AC1..ACn in spec | Stop; ask operator to add ACs |
| CLI edition map, for Fusebase Apps work | docs/fusebase-cli-edition.md | Continue with Flow-only planning, but mark CLI domain assumptions unknown |
| Letter prefix | AGENTS.md project-specific section | Default A; increment per ticket |
| T-counter | AGENTS.md project-specific section | Default T1; increment monotonically across all tickets |
docs/fusebase-cli-edition.md and list the CLI domain skills that should inform decisions, tasks, gate probes, or deploy handoff. Cite the relevant skill names; do not duplicate their runtime instructions in Flow artifacts.G1, G2, ... where G is the ticket's letter prefix).decisions.md using templates/decisions.md — ONLY if step 3 surfaced a real decision with alternatives (FR-23; otherwise omit the file). For each decision: recommendation, reasoning, alternatives considered (with rejection reasons), lock status PENDING. If the decision needs divergent product/UI/workflow alternatives, invoke flow-skills/design-discovery-ideation/SKILL.md first so the options are meaningfully different, not cosmetic variants.flow-skills/app-quality-patterns; the implementer reads the cited category before building). Non-UI tickets with QP-cited ACs (e.g., data-integrity QP-10..14) carry the IDs in the implement handoff instead.tasks.md using templates/tasks.md. Number tasks T, T<n+1>, ... starting from current T-counter. Mark dependency edges. Identify the verification-gate task (T) and deploy task (T). Module-size check (FR-25): every task names its target file(s). For each target over the policies/module-size.yml ceiling (or that the task would push over it), the task must either (a) state the extraction — new module name + the responsibility seam — or (b) carry a one-line exemption with reason for operator approval. "Where does this code live" is decided here, at Plan — mid-implement it is never asked, which is exactly how monoliths accrete. Full rule: flow-skills/module-size-discipline/SKILL.md.verification-gate.md using templates/verification-gate.md — when Full lane or gate policy requires it (FR-23). If user-facing/operator-facing smoke is needed, invoke flow-skills/smoke-testing/SKILL.md before writing S1..Sn. Include: gate-report required fields, outcome-based smoke prompts, probe list, rollback procedure.AGENTS.md. Update tasks.md SHAs to LOCKED.templates/handoff-implement.md (canonical); save to docs/tmp/handoff/<YYYY-MM-DD>-<slug>-implement.md BEFORE outputting in chat (FR-04). Per FR-23, the handoff points to canonical spec.md / decisions.md / tasks.md (cite paths + AC/decision IDs); it must NOT reprint their contents.| Artifact | Path | Mode |
|---|---|---|
| Decisions | docs/specs/<slug>/decisions.md | Mode B (full) |
| Tasks | docs/specs/<slug>/tasks.md | Mode B (full) |
| Verification gate | docs/specs/<slug>/verification-gate.md | Mode B (full) |
| Implement handoff | docs/tmp/handoff/<YYYY-MM-DD>-<slug>-implement.md | Mode B (full) |
| Updated counters | AGENTS.md project-specific section | Human-readable |
| Failure mode | Detection | Response |
|---|---|---|
| Spec lacks numbered ACs | scan spec.md for AC1.. | Stop; ask operator to add ACs to spec |
| Decision has no concrete alternatives | Single recommendation with no "Alternatives considered" rows | Surface this as a clarify Q rather than locking a single-option "decision" |
| Task chain has cycle | tasks.md dependencies graph has cycle | Stop; redraft to break the cycle |
| Constitution violation in plan | spec violates worker-undisturbed list or mixed-fleet rule | Stop; redirect spec OR amend project-specific rules |
| Frontend plan lacks real interaction contract | handoff names screens but not data/actions/API surfaces | Amend design brief before locking tasks |
| Frontend plan lacks selector strategy | UI smoke will need brittle text/CSS selectors | Add stable selector guidance before handoff |
requirements-specification re-invokeworkflows/architect-escalation.mddesign-discovery-ideation before locking decisionsrepo-onboarding-context-map for the unfamiliar area firstdecisions.md when no real decision was made (FR-23) — a single-option "decision" is not a decisiontasks.md or the handoff (FR-23) — point to the canonical ownerverification-gate.md when neither Full lane nor gate policy requires it (FR-23)Original Fusebase Flow content. Designed after reviewing public AI coding workflow patterns; no third-party code, prompts, skill files, or hook scripts are copied. See docs/source-map.md.
Use ONLY when the operator runs "/find-wasted-code" (or explicitly asks to "scan the repo for dead-end tool calls / broken links / missing helpers / footgun configs / silent push-through"). Statically scans THIS repo for friction footguns and writes a tracked report to docs/wasted-code/report.md. Manual-trigger ONLY — do NOT auto-invoke; the skill carries disable-model-invocation and no hook wires it. Read-only except the one report write. Findings are review candidates, never auto-fixes. Do NOT use for token/transcript economy (/token-waste-audit), for process ceremony (/find-wasted-effort), or for CLI/Flow drift health (/fusebase-health).
Use at Specify to classify a ticket Full vs Lightweight, and whenever a change looks small / reversible / low-risk ("small fix", "tweak", "hotfix", "drop pretty-printing", "bump a constant"). Operationalizes FR-21 — ceremony proportional to change size. Defines the eligibility gate, the change-note artifact, the one-pass build→verify→deploy procedure, and mid-flight promotion. Do NOT use for risky/uncertain work, schema/data migrations, security/permission changes, new public contracts needing a decision, unknown-root-cause diagnostics, or large features — those take the Full lane.
ALWAYS load at session start. After self-attesting, Read references/<role>.md for your role (Product Owner / AI Developer / Architect / Deploy phase) — role-specific don't-list, exact refusal phrasing for FR violations, and recovery pointers; shared cross-role protocols live in this file. Mandatory; not on-demand.
Use when the operator types /product-owner, asks to activate Product Owner, start a Product Owner or PO session, or searches /product in Codex for Fusebase Flow project management. Do NOT use for implementing code; route implementation to the AI Developer role.
Use when planning tasks that touch big source files, when an edit would push a file past the module-size ceiling, when the pre-commit module-size ratchet warns or blocks, or when generating policies/module-size-baseline.txt. Operationalizes FR-25 — module-size ratchet (ceiling default 800; over-ceiling files may shrink, never grow; extraction along a responsibility seam is in-scope, not scope creep). Do NOT use for docs/markdown size (FR-23 owns docs), to force decomposition of an existing monolith (that is its own explicit ticket), or to judge split quality by regex (seam-vs-mechanical is semantic — code-review owns it).
Use ONLY when verification passed AND operator explicitly says "prepare deploy" / "draft deploy" / "ship it"; drafts deploy handoff, captures deploy hash + probes + smoke, advises spec DRAFT→DONE flip. Do NOT auto-invoke; operator triggers explicitly.