boldaxolotl

booley-feedback

Prepare sanitized Booley feedback for manual submission from an offline container. Use for bugs, documentation contradictions, confusing behavior, opinions, or feature wishes. Investigate failures, provide a verified workaround where practical, and deliver a report with GitHub and maintainer email handoff options.

booley-ticket-create

Create a well-formed RTL development ticket from fuzzy requirements through interactive refinement

booley-ticket-triage

Interactive triage of blocked, failed, and review tickets

booley-add-to-qa

Turn human-provided public Booley behavior into reviewed Capability and Scenario Check changes.

booley-heal

Repair a Booley project's environment, configuration, and build-system health by running Doctor, resolving every actionable FAIL and WARN, reviewing packaged release changes after a version update, and verifying the result with plain and deep checks. Use when `booley doctor` is red or warning, an automatic Doctor notice reports problems, Booley reports a pending upgrade review, setup has drifted, a Booley Flow, Specialist, EDA tool, or Target stopped working, or the user asks to heal, repair, or make Doctor green. Hand host-only or otherwise external actions to the user with exact instructions, and route verified Booley or documentation defects through `booley-feedback`.

booley-setup

Perform design-aware Project Setup after Host Bootstrap and Project Initialization — plan first (feasibility + decision grill → SETUP-PLAN.md, Step 0), then execute gate-free (config, AGENTS.md, doctor audit — Steps 2–4). Phase-detects from the plan file; also runs a single step on request, or `new` for a from-scratch (`init --scaffold`) project with a lightweight grill. Post-gate Step 5 optionally cross-checks Booley's results against the repo's native build system; Step 6 always reports the run's findings and offers, once, to send the Booley-side ones upstream.

booley-qa-run

Execute one evidence-producing Booley public QA Scenario Run.