initiatives-workflow

name	initiatives-workflow
description	Use for full wave execution or durable wave/backlog state: delivery-map structure, packet schema, backlog entries, and closeout cleanup.

Initiatives Workflow

Owns durable wave, packet, delivery-map, backlog state, and full wave execution. Planning, review, delegation, and verification doctrine stay with their owner skills.

A wave may be one task. Use it when execution state must survive queue tracking, handoff, interruption, backlog/roadmap state, or multiple task cards.

References

• Read references/wave-packet-contract.md when packet, task-card, proof-row, or execution-state schema matters.

Owned State

• backlog to wave promotion
• delivery-map updates
• wave brief and packet maintenance
• backlog/mobile-parity follow-up state
• wave closeout cleanup
• full execution of one execution-ready wave

Paths And Statuses

• map: docs-ai/current-work/delivery-map.md

• brief: docs-ai/docs/initiatives/waves/<wave-id>.md

• draft packet: docs-ai/current-work/<wave-id>/wave-execution.draft.md

• canonical packet: docs-ai/current-work/<wave-id>/wave-execution.md

• backlog: docs-ai/current-work/backlog/<initiative>__<feature>__<item>.md

• discovery-required waves may have wave-execution.draft.md.

• Only execution-ready waves keep canonical wave-execution.md.

• Closeout removes delivery-map state and packet only after final review approves review coverage and verification approves the final claim.

• Completed wave briefs are disposable after retained invariants are extracted to the owning durable surface or valid backlog.

• Backlog entries store discovered separate debt and explicitly accepted temporary debt. They do not make current-scope blockers approvable.

• discovery-required: decisions still open; no canonical packet.

• execution-ready: planning gate approved; canonical packet exists.

• done: verified and final-reviewed; current-work packet can be cleaned.

• retired: intentionally closed without execution.

Execute A Wave

Before execution:

• wave brief status is execution-ready
• canonical wave-execution.md exists
• packet satisfies the wave packet contract
• durable brief and packet preserve original objective plus accepted reductions
• planning gate records real planning_critic and quality_guard approval

During execution:

• execute task cards in dependency order
• stop on discovery leakage, objective mismatch, owner defects that are not fixed/routed or explicitly accepted as temporary debt, or materially stale packet assumptions
• after each non-trivial implementation chunk, run required non-runtime proof and quality_guard before runtime proof, design review, final review, closeout cleanup, or the next non-trivial implementation chunk
• pass quality_guard the packet path, binding objective, changed surfaces, proof rows, commands run, touched-owner integrity verdict, and residual gaps

Before closeout:

• run wave-level verification and final isolated review
• ensure final claim does not exceed proof, runtime fidelity, or accepted scope
• remove packet state only after closeout is actually approved

Assets

• discovery brief: assets/wave-brief-discovery-required.md
• execution-ready brief: assets/wave-brief-execution-ready.md
• packet: assets/wave-execution.md
• backlog item: assets/backlog-entry.md

CLI

agent-harness wave bootstrap --repo-root <project-root> --wave <wave-id> --title "<title>"
agent-harness wave refs --repo-root <project-root> --wave <wave-id>
agent-harness wave cleanup --repo-root <project-root> --wave <wave-id>