ADW Pipeline Scripts

Complete reference for all ADW orchestrator and phase scripts.

Orchestrator Scripts

adw_plan_build.py

Combines planning and implementation phases.

uv run adw_plan_build.py <issue-number> [adw-id]

# Example
uv run adw_plan_build.py 42

Phases:

1. Planning — classify → spec → branch → PR
2. Building — implement from spec → commit → update PR

Equivalent to:

uv run adw_plan.py 42 | uv run adw_build.py

---

adw_plan_build_test.py

Plan + build + automated testing.

uv run adw_plan_build_test.py <issue-number> [adw-id]

Phases:

1. Planning
2. Building
3. Testing — run test suite → auto-fix failures (up to 3 attempts) → report

---

adw_plan_build_review.py

Plan + build + spec compliance review (no tests).

uv run adw_plan_build_review.py <issue-number> [adw-id]

Phases:

1. Planning
2. Building
3. Review — spec compliance check + Playwright screenshots + auto-patch blockers

When to use

Best for non-critical changes or when testing is handled separately. Review validates what was built against what was asked, without running the test suite.

---

adw_plan_build_test_review.py

Complete pipeline with both testing and review.

uv run adw_plan_build_test_review.py <issue-number> [adw-id]

Phases:

1. Planning
2. Building
3. Testing
4. Review

---

adw_sdlc.py

Full Software Development Life Cycle automation.

uv run adw_sdlc.py <issue-number> [adw-id]

# Flags
uv run adw_sdlc.py <issue> --skip-e2e         # skip browser tests (faster)
uv run adw_sdlc.py <issue> --skip-resolution  # review only, no auto-patch loop

Phases:

1. Plan — detailed implementation spec
2. Build — implement the solution
3. Test — comprehensive test suite with auto-fix
4. Review — spec compliance + screenshots + auto-patch
5. Document — generate app_docs/ from review artifacts

Output:

• Feature implementation on a PR-ready branch
• Passing tests
• Review report with screenshots
• Complete documentation in app_docs/

---

adw_plan_build_document.py

Fast documentation pipeline, skipping tests and review.

uv run adw_plan_build_document.py <issue-number> [adw-id]

WARNING

Documentation quality may be limited without review artifacts (no screenshots). Use adw_sdlc.py for comprehensive documentation.

---

Individual Phase Scripts

adw_plan.py

Planning phase only.

uv run adw_plan.py <issue-number> [adw-id]

What it does:

1. Fetches issue details from GitHub
2. Classifies issue type
3. Creates feature branch
4. Generates implementation plan
5. Commits plan as {adw_id}_plan_spec.md
6. Creates/updates pull request
7. Outputs state JSON to stdout

---

adw_build.py

Implementation phase. Reads from existing plan.

# Standalone (finds plan automatically)
uv run adw_build.py

# With piped state from adw_plan.py
uv run adw_plan.py 42 | uv run adw_build.py

# With explicit arguments
uv run adw_build.py <issue-number> <adw-id>

---

adw_test.py

Test phase with auto-fix loop.

uv run adw_test.py <issue-number> [adw-id] [--skip-e2e]

What it does:

1. Runs application test suite
2. Optionally runs E2E tests (browser automation)
3. Auto-resolves test failures (up to 3 attempts)
4. Reports results to GitHub issue
5. Commits test results

---

adw_review.py

Review phase — spec compliance check.

uv run adw_review.py <issue-number> <adw-id> [--skip-resolution]

What it does:

1. Locates specification file
2. Reviews implementation for spec compliance
3. Captures Playwright screenshots
4. Identifies issues (blockers, tech debt, skippable)
5. Auto-resolves blockers (unless --skip-resolution)
6. Uploads screenshots to Cloudflare R2 (if configured)
7. Posts detailed review report to GitHub

---

adw_document.py

Documentation generation phase.

uv run adw_document.py <issue-number> <adw-id>

Requirements: Completed review phase (needs review artifacts and screenshots).

What it does:

1. Analyzes implementation and review results
2. Generates technical documentation
3. Creates user-facing guides
4. Includes screenshots from review
5. Commits to app_docs/ directory

---

adw_patch.py

Quick patch workflow for targeted changes.

uv run adw_patch.py <issue-number> [adw-id]

Triggered by issues or comments containing the adw_patch keyword. Creates a targeted patch plan and implements specific changes without the full planning phase.

---

Primitive ADWs (No GitHub Required)

adw_prompt.py

Run any Claude Code prompt directly from the command line.

uv run adws/adw_prompt.py "Add logging to the main module"
uv run adws/adw_prompt.py "Refactor this function" --model opus
uv run adws/adw_prompt.py "List files here" --working-dir /path/to/project

adw_slash_command.py

Execute any .claude/commands/*.md template directly.

uv run adws/adw_slash_command.py /chore "Add error handling to all endpoints"
uv run adws/adw_slash_command.py /implement specs/my-plan.md --model opus

adw_chore_implement.py

Chains /chore (planning) → /implement (execution) without a GitHub issue.

uv run adws/adw_chore_implement.py "Add a health check endpoint to apps/server.py"
uv run adws/adw_chore_implement.py "Refactor the auth module" --model opus

adw_sdk_prompt.py

SDK-based interactive CLI. Supports one-shot queries and multi-turn sessions with session resumption.

# One-shot query
uv run adws/adw_sdk_prompt.py "Explain this codebase"

# Interactive session (multi-turn)
uv run adws/adw_sdk_prompt.py --interactive

# Resume a previous session
uv run adws/adw_sdk_prompt.py --interactive --session-id abc12345

# With specific tools enabled
uv run adws/adw_sdk_prompt.py "Create hello.py" --tools Write,Read,Bash

# Set initial context
uv run adws/adw_sdk_prompt.py --interactive --context "Debugging the auth middleware"