Delivery Harness Framework / Archive Only

Classic DHF Skill Routing Map.

Archive Only. This classic visual is kept for comparison. Use the Current Skill Routing Map for the primary public flow and current handoff links.

8standard lifecycle stages
9+helper / verification / brief entry points
3generic, repo-specific, gstack roles
4completion evidence fields

Archive Flow

Classic Mermaid flowchart retained for comparison; the current status-style page is the primary Flow Map.
flowchart TD
  Start(["User task enters
DHF"]) AGENTS["Read AGENTS.md
README and docs/repo-index.md"] Recover["Run harness_recover.py --json
restore phase, dirty state, next safe task"] Env["Run harness_env_probe.py --json
observe hooks, policy, schema"] NeedsReq{"Are goal, scope,
and acceptance clear?"} Req["Requirements lock
planner / req-to-dev / task-flow-orchestrator"] ReqVal["harness_requirements.py validate PATH"] Classify{"Classify lifecycle stage
and risk boundary"} Repo{"Repo-specific harness available?"} RepoSkill["Hand off to project adapter
business paths, commands, smoke matrix"] Product["Product / scope judgment
gstack-plan-ceo-review / gstack-office-hours"] Plan["Engineering / design planning
gstack-plan-eng-review / gstack-plan-design-review"] Dev["Implementation
tdd-guide / atdd-guide / scoped workers"] Team{"Parallel agents?"} TeamVal["harness_agent_team.py validate PLAN.json"] Val["Verification and evidence
verification-loop / harness_report.py / test_runner.py"] QA["QA / security / review
gstack-qa / gstack-cso / gstack-review / code-reviewer"] Ship["Ship / deploy
gstack-ship / gstack-land-and-deploy / gstack-canary"] Docs["Documentation release
gstack-document-release / doc-updater"] Handoff["Handoff
harness_checkpoint.py append"] Done(["DHF output
skill routing, verification evidence, next safe task"]) Start --> AGENTS --> Recover --> Env --> NeedsReq NeedsReq -- "No" --> Req --> ReqVal --> Classify NeedsReq -- "Yes" --> Classify Classify --> Repo Repo -- "Yes" --> RepoSkill --> Dev Repo -- "No, product-oriented" --> Product --> Plan Repo -- "No, engineering/design-oriented" --> Plan Repo -- "No, directly implementable" --> Dev Plan --> Team Dev --> Team Team -- "Yes" --> TeamVal --> Val Team -- "No" --> Val Classify -- "Verification" --> Val Classify -- "QA/security/review" --> QA --> Val Classify -- "Ship/deploy" --> Ship --> Val Val --> Docs --> Handoff --> Done classDef runtime fill:#edf3e9,stroke:#3f765b,color:#26372d; classDef decision fill:#eee9dc,stroke:#6f675e,color:#2b231d; classDef build fill:#f6e1ca,stroke:#b36a2f,color:#4a2e1e; classDef verify fill:#e7f0ea,stroke:#35796f,color:#26372d; classDef ship fill:#f4dde0,stroke:#a8425d,color:#51242f; class AGENTS,Recover,Env,ReqVal,TeamVal,Handoff runtime; class NeedsReq,Classify,Team decision; class Req,Plan,Dev,RepoSkill,Product build; class Val,QA,Docs verify; class Ship ship;

Skill Routing Map

Helpers provide objective runtime facts; skills provide cognitive workflow routing
Flow Step Primary Skill Helper Command When to Route Here
Start / recover delivery-harness-framework scripts/harness_recover.py --json
scripts/harness_env_probe.py --json
Any complex task, resumed session, dirty worktree, cross-stage handoff, or ambiguous request.
Requirements plannerreq-to-devtask-flow-orchestrator docs/templates/harness-requirements.md
scripts/harness_requirements.py validate PATH
CONTEXT.md / CONTEXT-MAP.md / ADR
The goal, scope, audience, constraints, domain vocabulary, success criteria, or acceptance tests are not locked.
Product / business judgment gstack-plan-ceo-reviewgstack-office-hours scripts/harness_requirements.py validate PATH when a requirement artifact exists User value, scope, demo boundary, priority, or business tradeoffs need to be clarified.
Engineering / design planning gstack-plan-eng-reviewgstack-plan-design-reviewplanner scripts/harness_agent_team.py validate PLAN.json when parallel work is proposed
docs/templates/harness-agent-brief.md when a worker needs a durable contract
Architecture, API, data flow, migration, visual structure, vertical slices, AFK/HITL, or multi-agent ownership must be decided.
Development tdd-guideatdd-guidescoped worker agents scripts/harness_agent_team.py validate PLAN.json
git status --short --branch
Acceptance criteria are clear and lifecycle policy allows scoped repo writes; worker briefs can validate current/desired behavior, key interfaces, and acceptance criteria.
Verification / evidence verification-loopharness_report.py python3 test_runner.py
git diff --check
scripts/verify_codex_env.sh ...
Before declaring completion, after code/config/docs changes, or when a debug task needs a runnable feedback loop first.
QA / review / security gstack-qagstack-qa-onlygstack-reviewcode-reviewergstack-csosecurity-reviewer git diff, scripts/harness_env_probe.py --json for runtime-sensitive work A diff exists, behavior is user-visible, a safety/privacy boundary is involved, or the work is close to handoff or release.
Ship / deploy / canary gstack-shipgstack-land-and-deploygstack-canary scripts/verify_codex_env.sh ...
scripts/harness_checkpoint.py append
The user explicitly asks for commit, PR, merge, release, deploy, or production validation.
Docs / handoff gstack-document-releasedoc-updaterdelivery-harness-framework scripts/harness_checkpoint.py append
scripts/harness_report.py --json
Docs need to reflect delivered behavior, or the session must persist next-safe-task state.

Routing Rules

1. Runtime facts outrank memory Run recovery and env probe first. Chat history and subconscious output are hints, not the only source of truth.
2. Requirements gate before planning If scope, acceptance criteria, or domain vocabulary are unstable, create or validate the requirements artifact and read CONTEXT.md / ADRs.
3. No parallel writes without a validator Any worker team must pass harness_agent_team.py validate to prove write sets do not overlap; add a durable brief when the task must survive handoff.
4. Completion claims require fresh evidence Before declaring completion, record command, exit_code, key_output, and timestamp; before debugging fixes, prove the feedback loop exists.
5. Handoff is a runtime event At the end of meaningful work slices, use harness_checkpoint.py append to record command, exit code, key output, timestamp, and next safe task.
6. Repos cannot force global sandbox truth Env probe may report observable sandbox and approval settings; it must not pretend to know hidden Desktop thread state.

Handoff Assets