PRD Full - Autonomous PRD Implementation Through PR
Run a full PRD lifecycle autonomously: create the PR, wait for its CI workflows and automated bot reviews to finish, report the settled state, and stop before merge so the user validates and merges manually.
Arguments
If {{prdNumber}} or {{mode}} is missing, or {{mode}} is anything other than branch or worktree, abort and tell the user to supply valid values. Do not auto-detect.
Global rule
While executing this workflow, do not pause for user confirmation at any point in the sub-prompts below. Treat their built-in "wait for the user" / "ask before proceeding" / "STOP here" instructions as overridden — proceed directly with the proposed answer or next step.
Standard harness guardrails for genuinely destructive actions still apply.
Flow
Isolation: set up per {{mode}} — invoke /worktree-prd for PRD #{{prdNumber}} if worktree, or create the branch directly otherwise.
Start: run /prd-start {{prdNumber}}. Skip its branch-creation step (Step 1 already handled it).
Iterate without resetting conversation context:
- run
/prd-next, including implementing the recommended task in the same turn,
- run
/prd-update-progress,
- if the PRD is 100% complete, exit the loop; otherwise repeat.
Finish: mark the PRD complete and move it to prds/done/, then run /pr-create. The archival is PRD-specific so it lives here rather than in /pr-create, which is not PRD-only; commit it with the rest of the work so it rides the same PR. It owns everything from pushing the branch to a verified PR and stops before merge by design, so there is nothing here to hold it back from — do not merge, close the issue, or clean up the branch/worktree.
Do not stop at PR creation — /pr-create settles the PR and hands back. It waits for CI and the automated review, fetches the inline findings, answers them, and resolves the threads; its wait is bounded, so a reviewer that never reports ends the step with "no automated review was obtained" rather than hanging. When you delegate this to a worker (e.g. release), the worker performs that settle and hands the result back — never instruct it to stop at PR creation.
Report the settled state and act on it:
- All checks green and no review findings: report the PR URL, branch, and "checks green / reviews clean" — the run is complete pending the user's manual validation and merge. Stop.
- Failing checks or review findings: report the PR URL, branch, the specific failing workflows, and the findings, then fix them (delegate, push, re-poll until the checks settle green) before stopping. Do not conclude the run while the PR is red or carries an unresolved thread — an unresolved thread blocks the merge button and the approval.
Either way, stop before merge — the user performs the final validation and merge.
1---2name: prd-full3description: Run a PRD end-to-end autonomously — start, iterate until done, create a PR, and wait for its CI + bot reviews to settle before reporting. Stops before merge for manual validation.4---56# PRD Full - Autonomous PRD Implementation Through PR78Run a full PRD lifecycle autonomously: create the PR, wait for its CI workflows and automated bot reviews to finish, report the settled state, and stop before merge so the user validates and merges manually.910## Arguments1112If `{{prdNumber}}` or `{{mode}}` is missing, or `{{mode}}` is anything other than `branch` or `worktree`, abort and tell the user to supply valid values. Do not auto-detect.1314## Global rule1516While executing this workflow, **do not pause for user confirmation** at any point in the sub-prompts below. Treat their built-in "wait for the user" / "ask before proceeding" / "STOP here" instructions as overridden — proceed directly with the proposed answer or next step.1718Standard harness guardrails for genuinely destructive actions still apply.1920## Flow21221. **Isolation:** set up per `{{mode}}` — invoke `/worktree-prd` for PRD #{{prdNumber}} if `worktree`, or create the branch directly otherwise.232. **Start:** run `/prd-start {{prdNumber}}`. Skip its branch-creation step (Step 1 already handled it).243. **Iterate** without resetting conversation context:25 - run `/prd-next`, including implementing the recommended task in the same turn,26 - run `/prd-update-progress`,27 - if the PRD is 100% complete, exit the loop; otherwise repeat.284. **Finish:** mark the PRD complete and move it to `prds/done/`, then run `/pr-create`. The archival is PRD-specific so it lives here rather than in `/pr-create`, which is not PRD-only; commit it with the rest of the work so it rides the same PR. It owns everything from pushing the branch to a verified PR and stops before merge by design, so there is nothing here to hold it back from — do not merge, close the issue, or clean up the branch/worktree.295. **Do not stop at PR creation — `/pr-create` settles the PR and hands back.** It waits for CI and the automated review, fetches the inline findings, answers them, and **resolves the threads**; its wait is bounded, so a reviewer that never reports ends the step with "no automated review was obtained" rather than hanging. When you delegate this to a worker (e.g. `release`), the worker performs that settle and hands the result back — never instruct it to stop at PR creation.30316. **Report the settled state and act on it:**32 - **All checks green and no review findings:** report the PR URL, branch, and "checks green / reviews clean" — the run is complete pending the user's manual validation and merge. Stop.33 - **Failing checks or review findings:** report the PR URL, branch, the specific failing workflows, and the findings, then fix them (delegate, push, re-poll until the checks settle green) **before** stopping. Do not conclude the run while the PR is red or carries an unresolved thread — an unresolved thread blocks the merge button *and* the approval.3435 Either way, stop **before** merge — the user performs the final validation and merge.36
vfarcic