Agentic Spec Confirmed Implementation
Use rules/phase65-trigger.md for the complete trigger and non-trigger
decision. This skill runs Path A fenced JSON requests directly after
validation, and runs Path B only after the Agent has assembled the full request
JSON, shown it to the user, received explicit confirmation, validated it, and
passed the final same-phase manifest recheck.
Required Context
rules/phase65-trigger.mdrules/request.mdrules/planning.mdrules/execution.mdrules/review-gap-policy.mdrules/remote-sync-ci.mdrules/manual-doc-handoff.mddocs/solutions/l3/detail/phase6-5a-spec-confirmed-implementation-automation-graphify-chain-analysis.md
Workflow
Prepare (prepare): use validated request JSON as the input, with Path A
fenced JSON and Path B assembled JSON as the upstream sources; validate the
request and manifest, run agentic-spec doctor, execute confirm guard,
confirm exactly one plan, confirm codex-agentic P0 detached support, and
resolve ExecutionRefs.phase_id, plan refs, confirm commit, and phase refs
before any executor start.
Start detached (start detached): run:
codex-agentic --automation phase-confirmed --detach --result docs/assets/builder/executions/<phase-id>.codex-agentic-run.yaml <plan_ref>
Capture and persist the execution handle JSON emitted by the detached start.
The handle, not terminal prose, is the control-plane correlation object.
Monitor/closeout (monitor/closeout): read detached lifecycle evidence from
the normalized execution store and the phase run-result. Do not infer machine
state, merge readiness, review status, push completion, cleanup completion, or
CI handoff from stdout prose, HUD text, or terminal summaries.
Blocked intervention (blocked intervention): when lifecycle status is
blocked, report the blocked reason code, safe evidence refs, and the
lifecycle or prompt action type required for the next human decision.
Compatibility fallback for pre-S3 environments only: if detached P0 support is
unavailable and the confirmed request explicitly allows legacy operation, the
foreground command remains:
codex-agentic --automation phase-confirmed --legacy-foreground --result docs/assets/builder/executions/<phase-id>.codex-agentic-run.yaml <plan_ref>
Foreground stdout is never an automation decision contract.
Guardrails
- Do not ask for a second plan approval.
- Do not parse human-readable
codex-agentic stdout or HUD text as the decision contract.
- Do not force push.
- Do not auto-patch app workspace
AGENTS.md or docs/solutions.
- Do not put semantic decisions into
agentic-spec.
1---2name: agentic-spec-confirmed-implementation3description: Orchestrate a Phase 6.5 confirmed implementation request from either a fenced JSON spec-confirmed-implementation-request or an explicit natural-language automation request after request assembly and confirmation; bare acknowledgements do not trigger this skill.4---56# Agentic Spec Confirmed Implementation78Use `rules/phase65-trigger.md` for the complete trigger and non-trigger9decision. This skill runs Path A fenced JSON requests directly after10validation, and runs Path B only after the Agent has assembled the full request11JSON, shown it to the user, received explicit confirmation, validated it, and12passed the final same-phase manifest recheck.1314## Required Context1516- `rules/phase65-trigger.md`17- `rules/request.md`18- `rules/planning.md`19- `rules/execution.md`20- `rules/review-gap-policy.md`21- `rules/remote-sync-ci.md`22- `rules/manual-doc-handoff.md`23- `docs/solutions/l3/detail/phase6-5a-spec-confirmed-implementation-automation-graphify-chain-analysis.md`2425## Workflow26271. Prepare (`prepare`): use validated request JSON as the input, with Path A28 fenced JSON and Path B assembled JSON as the upstream sources; validate the29 request and manifest, run `agentic-spec doctor`, execute confirm guard,30 confirm exactly one plan, confirm `codex-agentic` P0 detached support, and31 resolve `ExecutionRefs.phase_id`, plan refs, confirm commit, and phase refs32 before any executor start.332. Start detached (`start detached`): run:3435 ```text36 codex-agentic --automation phase-confirmed --detach --result docs/assets/builder/executions/<phase-id>.codex-agentic-run.yaml <plan_ref>37 ```3839 Capture and persist the execution handle JSON emitted by the detached start.40 The handle, not terminal prose, is the control-plane correlation object.413. Monitor/closeout (`monitor/closeout`): read detached lifecycle evidence from42 the normalized execution store and the phase run-result. Do not infer machine43 state, merge readiness, review status, push completion, cleanup completion, or44 CI handoff from stdout prose, HUD text, or terminal summaries.454. Blocked intervention (`blocked intervention`): when lifecycle status is46 blocked, report the blocked reason code, safe evidence refs, and the47 lifecycle or prompt action type required for the next human decision.4849Compatibility fallback for pre-S3 environments only: if detached P0 support is50unavailable and the confirmed request explicitly allows legacy operation, the51foreground command remains:5253```text54codex-agentic --automation phase-confirmed --legacy-foreground --result docs/assets/builder/executions/<phase-id>.codex-agentic-run.yaml <plan_ref>55```5657Foreground stdout is never an automation decision contract.5859## Guardrails6061- Do not ask for a second plan approval.62- Do not parse human-readable `codex-agentic` stdout or HUD text as the decision contract.63- Do not force push.64- Do not auto-patch app workspace `AGENTS.md` or `docs/solutions`.65- Do not put semantic decisions into `agentic-spec`.
dolphinai2026