jchilders

Decompose a milestone/spec directory into beads issues (features + task + dependency graph) as a dry-run plan. User reviews and approves before any `bd create` fires. Use when the user points at a spec doc or directory and asks for a bead breakdown, task graph, or project plan. One bead per task doc (type=feature), plus one bead for milestone-level end-to-end acceptance (type=task). Dry-run is the default — never create beads without explicit approval.

Drive Citadel in a real browser session and capture deterministic screenshots. Use when the task requires visual proof of Citadel behavior, command expansion, suggestion chips, output rendering, or UI regressions in the demo app by running keyboard command flows and saving PNG screenshots.