fagan-inspection-beads

Run a Fagan Inspection on the current change set, then create Beads issues from the defect log so defects become trackable tasks.

This is an add-on to fagan-inspection. Run the full five-phase inspection first, produce the consolidated defect log, then pipe defects into Beads.

Operating rules

• Default to review mode, not implementation mode. Do not edit code unless the user explicitly asks for rework after the inspection.
• Prefer findings about bugs, regressions, missing tests, design risks, and operational hazards over summaries.
• When subagents are available, use them only for independent domain reviews. Keep scope selection, synthesis, severity decisions, and Beads creation local.
• Keep commands non-interactive. Use bd create, bd update, bd dep add, and bd ready --json; never rely on editor-based flows.

Phase 1: Run the Fagan Inspection

Execute all five phases of a standard Fagan Inspection (scope, plan, domain reviews, synthesis, rework). Produce the full Fagan Inspection Report with the consolidated defect log table before proceeding.

Use existing chat context for intent and acceptance criteria. If missing, derive scope from git (status, staged/unstaged diff, PR-range diff vs origin/main or origin/master).