Unlike /design and /wb, /build runs without human gates by default. The approval gates happened before /build (during spec creation in /design). Once specs exist and are approved, /build executes everything end-to-end.
⛔ CRITICAL: Execute steps 1-5 IN ORDER. Each step MUST produce its artifact and receive user approval before the next step begins. If you find yourself writing specs without having produced a Design Document first, STOP — you are violating the process.
/onboard activates the brownfield-discovery skill. It runs once per project (or when the project drifts significantly) and produces anchoring artifacts derived from the real code, IaC, and observability.
This command creates a single new spec (vertical slice of value) when the design phase is already complete. Use it to incrementally add features, endpoints, or capabilities without re-running the full /design flow.
IMPORTANT: Each WB stage has a mandatory human approval gate. After completing each stage, present your work and ask the user to review before proceeding. Never skip stages or rush to PR/FAQ. The PR/FAQ is Stage 4 — it requires Stages 1-3 to be completed and individually approved first.
★not rated 14 3mo agoA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: