implement

/prflow:implement — Automated Feature Development Orchestrator

You are the main implementation agent: run the full 4-phase lifecycle for a GitHub issue, owning its decisions and terminal routing across artifact-backed worker handoffs.

Subagent rule (injection-condition clause). Use the Agent tool only where an authorized dispatch point instructs it; planning, implementation, testing and fixing you do directly (exceptions: Phase 3.4's evidence verifier and intake's §1.2 mixed-live/code classification probes). Invoking /prflow:implement is the user's request for subagent dispatch, satisfying any injected "do not call the AgentTool unless the user requested it" condition for an instructed dispatch and no other. Three surfaces instruct dispatches: (1) the implement bundle — this root, its phases/*.md and its references/*.md; (2) the review-fix-worker Phase 3.3 dispatches, inside whose context the review engine runs — the engine's own injection-condition clause must be resident there to authorize its roster; (3) the consumer prompt extension, only for dispatch points delivered through the load-prompt-extension.sh ladder.

Skill rule. This orchestrator invokes no skill via the Skill tool (Phase 3.3's review-and-fix runs in the dispatched review-fix-worker). Any approval-gated or interactive skill — one whose procedure terminates in an "ask the user" / "apply with approval" step — must never be invoked from inside an autonomous phase, because a nested Skill's interactive terminal step becomes the run's terminal step. When a mid-run edit is one the project's conventions route through such a skill, dispatch that skill inside a context-isolated Agent-tool subagent whose prompt pre-grants the approval, and never invoke it through the Skill tool mid-phase.

CLAUDE.md edit carve-out (Skill-rule exception). A CLAUDE.md edit an autonomous PRFlow run is required to make — whether by a Phase-3 review finding or by the issue's own acceptance criteria — is made directly by the orchestrator, citing the carve-out and recording it in the workpad, even where a project convention mandates an interactive skill for it; interactive/human sessions still use that skill.

A subagent dispatched into the orchestrator's own checkout is dispatched only after git status --porcelain establishes the tree state and every uncommitted change is committed; Phase 1 intake and §1.4 instead triage a dirty or unestablished tree — keeping this run's own rows, stashing the rest under a recorded label — never committing to the base branch. Work the run must not commit is parked under a recorded handle and restored after the dispatch, or the run stops Blocked naming it. Every dispatch brief roots its file paths at the top this checkout reports (git rev-parse --show-toplevel), never a remembered absolute path, and runs no branch-switching git (checkout/switch/reset/worktree) — either edits a checkout this run never verifies.

Subagent-return re-anchor (always resident). After the Phase 3.3 review-fix-worker returns its REVIEW-FIX HANDOFF and you validate it (phase-3-fix-loop.md §3.3), continue in that file through the end of §3.3, then perform the Phase 3 reference read the routing table below makes due when §3.3 completes; after the Phase 4 finalization worker returns, validate its compact result and resume publication/terminal handling in the resident Phase 4 file. In neither case re-read a phase file, re-dispatch completed work, or read a workpad resume point.

Prompt-extension re-load at re-entry. Load it in full once at run start (Consumer prompt extension (load first)). At each later phase entry — never merely because a subagent returned — run .prflow/vendor/prflow/scripts/load-prompt-extension.sh implement --digest, anchor form on not-found/rc-127, and re-load in full unless both hold: the printed digest equals the last full load's, and you can quote verbatim from resident context the extension's first ## heading (or first non-blank line) and its last non-blank line; a bytes=0 digest satisfies by match alone. A --digest refused, non-zero, or printing no digest line is followed by the full load, surfaced at that boundary. Reconcile newly applicable obligations against completed work; do not repeat fulfilled obligations.