addy-auto-unblock

Files (1)

• SKILL.md

SKILL.md (first lines)

# Addy Auto Unblock

Use this only inside `/addy-auto`.

## Non-negotiable rule

Do not trade correctness for progress. Never skip, weaken, or silently reinterpret acceptance criteria, verification, or review just to unblock the loop. `[x] Verified` and `[x] Reviewed` require real evidence from this run.

## Recovery loop

Before pausing:

1. Load and apply `debugging-and-error-recovery`.
2. Reproduce the blocker with the exact failing command, review finding, missing artifact, or git state.
3. Classify the blocker:
   - implementation defect
   - test/fixture/tooling gap
   - build-time missing ADR/spec/steering context that can be repaired by linking an existing unambiguous artifact
   - review finding needing a code or test fix
   - ADR-related review finding needing implementation repair, missing spec/plan required context, or an existing ADR link
   - plan/status checkbox out of sync with evidence
   - workflow state/stat synchronization lag where the plan already has the owned checkbox checked and this run has real phase evidence
   - genuinely unsafe or ambiguous decision
4. Fix the root cause when the fix is safe and scoped to the current task.
5. Add or update meaningful regression coverage when behavior changed.
6. Re-run the required verification/review step.
7. Update only the lifecycle checkbox owned by the completed step.

ADR-related review findings are recoverable when the safe scoped fix is to preserve an existing ADR, restore a skipped `must not` guardrail, or add missing references to an already-existing ADR in the spec/plan required context. Pause instead of auto-fixing when resolution requires creating or superseding an ADR, choosing between conflicting ADRs, or making a product/security/architecture judgment.

Build-time missing ADR/spec/steering context is recoverable only when the existing ADR or steering file is unambiguous and the safe scoped fix is limited to linking it from the active spec/plan required context. After repairing that context, rerun the blocked build step. Pause instead of redesigning during build or guessing; if re-defining the spec, a new/superseding ADR, conflicting ADR interpretation, or human architecture/product/security judgment is needed, stop and report the blocker.

If the repeated blocker is "missing lifecycle evidence: Reviewed" but the active task already has `[x] Reviewed` and the latest real `/addy-review` for that task reported `No issues found`, do not re-run review just to satisfy stale state. Treat it as synchronization lag, preserve the review evidence in the report, and let Addy auto commit or advance to the next unfinished slice.

## Missing or failing verification artifacts

Missing test files, fixtures, commands, snapshots, generated docs, or local setup are not automatic blockers.

- If the artifact is required by the current acceptance criteria, create or repair it with meaningful assertions.
- If the artifact is stale or over-broad, preserve the acceptance criteria and replace it only with equivalent or stronger verification evidence. Record why in the plan.
- Do not create placeholder tests, empty fixtures, or assertions that cannot fail when the required behavior regresses.

## Auto-dispatched fix-all handoff

When `/addy-fix-all` runs inside `/addy-auto`, it is only the fix pass. Fix the surfaced review issues and run narrow validation for the changed scope, then stop. Do not invoke or perform `/addy-verify` or `/addy-review` inside that fix-all turn. The auto monitor owns the follow-up order: `/addy-verify`, then `/addy-review`.

## When to pause

Pause only after the recovery loop when:

- the next step is destructive, external, or needs credentials the agent does not have;
- the acceptance criteria conflict or require product/security/architecture judgment;
- the only apparent fix would weaken verification or review;
- the failure cannot be reproduced with available evidence;
- repeated root-cause fixes fail and further attempts would be speculative.

When pausing, report the exact blocker, evidence gathered, commands run, and the safest next action.

From teknologist/pi-addy-workflow, MIT.

More from teknologist/pi-addy-workflow