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
requirements-phase: human-centered discovery throughrequirements-grillandwrite-backlog.delivery-phase: resumable scoped delivery through phase modules for spec, plan, implementation, review, optional debugging, docs ingest, and closeout.review-phase: readonly-by-default findings-first review starting withreviewStandards versus Spec axes, usingautoreviewas runtime, then applying architecture, simplification, scoped guidance, and validation lenses.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.
Backlog Hierarchy Contract
Requirements and delivery phases share one backlog hierarchy: EPIC plus child stories or sub-issues.
requirements-phase ends by using write-backlog to format accepted requirements into EPICS and their child stories or sub-issues. delivery-phase then targets the EPIC as the parent capability and requires create-spec, create-plan, and implement-spec to preserve every child-story or sub-issue requirement.
The EPIC is not a loose theme. A child story or sub-issue is not a throwaway link. The EPIC anchors the spec, and each child story or sub-issue contributes requirements, constraints, acceptance criteria, ordering, or non-goal context to that spec and its plan.
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.
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.