Phase Wrappers
Optional workflow wrappers that preserve lifecycle order and closeout evidence
Phase wrappers are optional workflow entrypoints.
A manual Harness flow can call the individual skills one by one. A phase wrapper bundles that same workflow into a bounded orchestration unit, while the delegated inner skills keep their own proof standards and stop conditions.
Phase wrappers preserve order through progressive routing. They should choose the current gate from repo, tracker, and artifact state before loading child skills. Naming the lifecycle sequence is allowed; front-loading every child skill contract at wrapper start is not.
delivery-phase is a resumable phase router. Its entrypoint reads the router module, chooses one selected phase module, lets that phase write handoff state, then stops or re-enters routing. This means manual HITL steps and AFK delivery use the same artifacts instead of separate workflows.
Manual And AFK Use
Manual flow gives the operator the most explicit step-by-step control. The operator can call requirements, spec, plan, implementation, review, debugging, and docs ingest skills separately, checking the output and validation evidence at each boundary.
AFK or Ralph-like flow moves that step-by-step discipline into a bounded run. /goal is the outer execution mode. A phase wrapper is the lifecycle unit named inside that mode, such as delivery, debugging, review, docs ingest, or debt resolution.
Phase Units
business-finder: human-only optional Business-intake profile over the shared Finder engine; it may project Product Areas and Initiatives.functional-finder: human-only optional Functional-intake profile over that engine; it may project Business structure plus Epics.finder-phase: the shared resumable Fog graph composed directly by those wrappers; it is also human-only and never a model-selected root route.requirements-phase: sole route throughrequirements-grill,create-spec, and delivery-depthwrite-backlogprojection.delivery-phase: resumable scoped delivery through phase modules for spec, plan, implementation, optional debugging, docs ingest, and closeout. At its review gate it persistsreview_dueand stops for explicit review; a later explicit resume consumes retainedreview_routedevidence.review-phase: explicit-only readonly review of one frozen Git/diff or standalone artifact bundle. It runs one advisoryautoreview, verifies candidates through all mandatory lenses in parallel, retains one immutable report, returns routing, and stops.debugging-phase: runtime-evidence debugging through logs, repros, optional readonly parallel research, bounded fixes, and regression validation.bug-discovery-phase: AFK ClawPatch discovery, report generation, and triage without source mutation by default.bug-resolution-phase: selected ClawPatch finding classification and bounded resolution through normal Harness edits by default.docs-ingest-phase: routed wiki/project docs, navigation, ingest metadata, and root docs alignment after proven changes.resolve-debt-phase: resolution of one concrete tech-debt artifact through the delivery workflow.
goalify sits beside these phases as the prompt compiler for /goal mode.
Finder And Backlog Contract
The two Finder wrappers are optional intake profiles over one finder-phase state graph. Delivery-depth work belongs to Requirements Phase:
Business -> optional Product Area / Initiative
Functional -> optional Business structure + Epic
Requirements Phase -> Requirements Grill -> SPEC.md outcomes (`OUT-###`)
-> derived Epic / Story / Task identities + blockersFog stays lateral to the product hierarchy and remains open after every Finder target-depth return. $write-backlog is the sole provider writer. It reconciles existing structure before create, enriches by stable provider and durable wiki identity, and requires preview plus explicit approval for structural changes.
Delivery preserves the provider Task identities and native blocker graph derived by Write Backlog from the retained specification. It records directly observed start, blocker, pull-request, merge, staging, and production facts as distinct evidence. Production evidence for all accepted resulting Stories and Tasks completes the Fog; merge does not.
Prompt Boundary
Phase wrappers should not appear as scoped AGENTS.md primary skills. Scoped prompts should name local execution and review skills that apply to a code area. Parent goals and handoffs should name phase wrappers when they want full lifecycle orchestration.
Finder is narrower still: a human explicitly invokes the chosen Business or Functional wrapper. Root guidance and model routing do not select one implicitly.
This boundary keeps local prompts focused and avoids making every scope look responsible for every lifecycle phase.
ClawPatch bug lifecycle phases follow the same boundary. They are global entrypoints for parent goals and handoffs, not scoped primary-skill lines.
Validation Evidence
Validation gates come from the inner skills. The wrapper delegates to those contracts for proof standards, valid no-op reasons, and blocker conditions.
The wrapper's job is to preserve the workflow order and collect the resulting evidence into a coherent lifecycle report.