Delivery Phase Progressive Routing Grill Log

Source issue: harness-intelligence#33

Branch A: Phase Activation Semantics

Q1

Question: Should delivery-phase be a one-file wrapper with better progressive-disclosure wording, or a reusable router skill with phase subfiles?

Accepted answer:

• delivery-phase is a reusable router skill.
• SKILL.md stays concise and points first to phases/router.md.
• Phase behavior lives in separate phases/*.md files.
• Delivery start reads only the entrypoint, the router, and enough repo/tracker/artifact state to select one next phase.
• The selected phase file may then delegate to the relevant child skill.

Q2

Question: Should completing one phase imply continuing through the rest of the delivery chain?

Accepted answer:

• No. Phase completion writes a resumable phase handoff, then stops or re-enters delivery-phase.
• Re-entering delivery-phase means the router inspects current state again and chooses the next phase from evidence.
• This supports both AFK/full-delivery flow and human-in-the-loop checkpoints.

Q3

Question: What entrypoints should this architecture support?

Accepted answer:

• Direct phase entrypoints remain valid: create-spec, create-plan, implement-spec, review-phase, debugging-phase, and docs-ingest-phase.
• delivery-phase can be invoked after any direct phase to resume from durable artifact state.
• Manual/HITL control means the user can run spec and plan manually, then invoke delivery-phase; the router should detect those artifacts and continue from implementation, review, docs ingest, or closeout.

Q4

Question: Which files define the modular delivery skill?

Accepted answer:

• SKILL.md is the concise entrypoint.
• phases/router.md chooses the next phase.
• phases/spec.md, phases/plan.md, phases/implement.md, phases/review.md, phases/debug.md, phases/docs-ingest.md, and phases/closeout.md own their phase contracts.
• references/artifact-state.md defines phase-complete evidence.
• references/phase-handoff.md defines resumable handoff shape.

Glossary Q5

Question: What is the canonical term for the fixed behavior?

Accepted answer:

• Canonical term: Resumable phase router — a phase wrapper entrypoint that chooses one next lifecycle phase from durable artifacts and evidence, then stops or re-enters after that phase writes state.
• Related term: Progressive phase routing — the loading strategy used by the resumable phase router.
• Avoid: eager wrapper graph, eager orchestration graph, front-loaded phase chain.
• Relationship: Resumable phase router uses Progressive Disclosure and supports HITL checkpoints.
• Axiom: A phase wrapper can preserve lifecycle order without owning every step in one uninterrupted run.

Closure

The requirements branch is closed. Implementation is the modular delivery-phase skill in /Users/stefan/Desktop/repos/wearedevpunks-skills, synced into Harness skill mirrors.