PR Doctor Skill — Redirect

The pr-doctor body (CI wait, multi-source fetch over build / PR comments / Sonar, per-finding triage) lives in `plan-marshall:plan-marshall/workflow/verification-feedback.md` § Step 1 under producer=pr-state. The triage core (FIX / SUPPRESS / ACCEPT / AskUserQuestion) lives in `plan-marshall:plan-marshall/workflow/triage.md` Steps 1-6.

Enforcement

Execution mode: Dispatch verification-feedback.md with producer=pr-state; do not implement the body here.

Prohibited actions:

• Do not duplicate the pr-state body in this file — verification-feedback.md is the single source of truth.
• Do not invoke this skill directly from manifest steps — the phase-6-finalize finalize loop dispatches verification-feedback directly.

Constraints:

• The slash-command surface (/workflow-pr-doctor) MUST resolve through manage-config effort resolve-target --phase phase-6-finalize --role verification-feedback and dispatch the canonical executor variant.

Dispatch

When /workflow-pr-doctor is invoked, resolve the level + target via:

python3 .plan/execute-script.py plan-marshall:manage-config:manage-config \
  effort resolve-target --phase phase-6-finalize --role verification-feedback

Emit the standardized post-resolve dispatch log line — see `../ref-workflow-architecture/standards/dispatch-logging.md` § Emission contract:

python3 .plan/execute-script.py plan-marshall:manage-logging:manage-logging \
  work --plan-id {plan_id} --level INFO \
  --message "[DISPATCH] (plan-marshall:workflow-pr-doctor) target={target} level={level} role=verification-feedback workflow=plan-marshall:plan-marshall/workflow/verification-feedback.md plan_id={plan_id}"

Then dispatch the returned target (execution-context-{level} or canonical) with this prompt body:

name: workflow-pr-doctor
plan_id: {plan_id}                # current plan or unset for standalone runs
workflow: plan-marshall:plan-marshall/workflow/verification-feedback
skills:
  - plan-marshall:manage-findings
  - plan-marshall:manage-tasks
  - plan-marshall:manage-architecture
  - plan-marshall:manage-config
  - plan-marshall:tools-integration-ci
  - plan-marshall:workflow-integration-git
  - plan-marshall:workflow-integration-github
  - plan-marshall:workflow-integration-sonar
WORKTREE: {worktree}
producer: pr-state
pr_number: {pr_number}            # required; auto-detect via `ci pr view` when absent
caller_phase: phase-6-finalize

The dispatched envelope runs verification-feedback.md Step 1 (producer=pr-state branch) inline and continues into the triage core.

Output

Pass-through from verification-feedback.md:

status: success | loop_back | error | ci_failure
display_detail: "<≤80 char summary, e.g. 'PR #123 diagnosed, 2 issues, 1 fix applied'>"
producer: pr-state
findings_processed: {N}
findings_resolved: {M}
fix_tasks_created: {K}

Canonical invocations

The canonical argparse surface for pr_doctor.py. The plugin-doctor analyzer (_analyze_manage_invocation.py) reads this section as source-of-truth for the manage-invocation-invalid and missing-canonical-block rules. Consuming docs xref this section by name instead of restating the command inline. See `pm-plugin-development:plugin-script-architecture` cross-skill-integration.md § "Script invocation in documentation".

track-attempt

python3 .plan/execute-script.py plan-marshall:workflow-pr-doctor:pr_doctor track-attempt \
  --category {build,reviews,sonar} --current CURRENT [--max-attempts MAX_ATTEMPTS]

diagnose

python3 .plan/execute-script.py plan-marshall:workflow-pr-doctor:pr_doctor diagnose \
  [--build-status {success,failure}] [--build-failures BUILD_FAILURES] \
  [--review-comments REVIEW_COMMENTS] [--sonar-issues SONAR_ISSUES]

parse-handoff

python3 .plan/execute-script.py plan-marshall:workflow-pr-doctor:pr_doctor parse-handoff \
  --handoff HANDOFF [--pr PR] [--checks {build,reviews,sonar,all}] \
  [--auto-fix] [--wait] [--no-wait] [--max-fix-attempts MAX_FIX_ATTEMPTS]

Related

• `verification-feedback.md` — orchestrator body.
• `triage.md` — canonical per-finding decision + action loop.
• `standards/automated-review-lifecycle.md` — phase-6-finalize automated-review variant (now a thin sibling of producer=pr-comment in verification-feedback.md).