PABCD Workflow Default Active

P — Plan User Approval Required

The planning phase reads project docs and dev skills, then produces a plan with two parts:

• Part 1 — Easy explanation: What will be built, in non-developer terms. Anyone should understand this.
• Part 2 — Diff-level precision: Exact file paths (NEW / MODIFY / DELETE), before/after diffs for MODIFY, complete content for NEW.

Scope Clarification

If the request has unclear scope or unspecified technology, the planner clarifies first:

• Presents 2-3 options as <TechName> -- <plain explanation>
• Recommends one with project-specific reasoning
• Confirms once, then proceeds

Repository Scan (broad changes)

For broad changes or unfamiliar repositories, the P phase MUST include:

• Compact tree of the current repository shape
• Detected repo conventions: docs, plans, architecture notes, source-of-truth logs, naming, tests
• Whether existing structure/, devlog/, docs/, plans/, or equivalent logs were read and will be reused
• Whether structure/ or devlog/ is proposed

Devlog Naming Convention

If PABCD work creates or updates devlog/ plan artifacts, the plan MUST list exact numbered Jawdev filenames:

00_overview.md
01_phase1_<slug>.md
02_phase2_<slug>.md

Bare filenames like PLAN.md, DIFF_PLAN.md, PHASES.md, RCA.md, or plan.md are not allowed as new devlog phase files.

Gate Questions

Before presenting the plan, the planner asks:

1. "Any business logic I shouldn't decide alone?"
2. "Does Part 1 match your intent?"

The plan is presented and revised on feedback. When the user approves, transition with cli-jaw orchestrate A.

A — Plan Audit User Approval Required

A worker is spawned to audit the plan (not the code). The worker verifies:

• All file paths and imports in the plan actually exist
• Function signatures match real code
• No integration risks
• Existing source-of-truth docs/logs were read when present
• No new structure/, devlog/, docs, or AGENTS files are introduced without user approval
• New JS/TS files follow TypeScript preference rules unless the plan states why JS is required
• New TypeScript is strict-compatible or limitations are stated
• New devlog phase documents use the numbered Jawdev filename convention

Worker outputs JSON for the audit. Results are reviewed:

• FAIL → Fix the plan, re-audit
• PASS → Report results to the user

When the user approves, transition with cli-jaw orchestrate B.

B — Build User Approval Required

Implementation phase. The boss writes all code directly. Workers are read-only verifiers only.

After implementing, a worker is dispatched for verification — checking that code exists and integrates cleanly:

• NEEDS_FIX → Boss fixes the issues, re-verifies
• DONE → Report results to the user

Does not create structure/ or devlog/ unless approved in P or explicitly requested.

When the user approves, transition with cli-jaw orchestrate C.

C — Check Auto-advance

Final sanity check that runs automatically:

1. Verify all files saved and consistent
2. Run npx tsc --noEmit (if TypeScript project)
3. Update project structure docs if applicable
4. Report completion summary

When done, automatically transitions to D via cli-jaw orchestrate D.

D — Done Auto-advance

Summarizes the entire PABCD flow:

• What was planned (P), audited (A), built (B), checked (C)
• List of files changed
• Any follow-up items

State returns to IDLE automatically.