Implement a solution write-up (typically the markdown file produced by /solve-me) in this Laravel project, following existing project patterns and Laravel best practices. Cuts the work into commits itself, writes the commit plan to docs/build/ .md, and gets the developer's approval before writing any code. Then builds…
Ruthlessly eliminate comprehension debt before design or implementation. Use when the developer wants to stress-test a plan, decision, requirement, bug, feature, architecture, or implementation idea. The developer must demonstrate that they understand the problem, constraints, behavior, and consequences in their own…
Check that a built feature actually matches the original problem (/grill-me) and the chosen solution (/solve-me). Acts like a real user and a QA engineer, not a code reviewer: confirms scope, environment, database safety and login with the developer first, then creates real dummy data in the database (via Laravel…
Writes a PR title and description to .workflow/ /pr.md from the branch's commits, the plan and the recorded verification. Use when opening a PR or asked for a PR description.
Turns a feature idea into a product decision - who, which metric, what cost, smallest sellable slice - at .workflow/idea- /frame.md. Use when a feature is proposed with no ticket or agreed scope.
Turns .workflow/ /triage.json and the code into an audited implementation spec at .workflow/ /sdd.json. Use before writing code for a ticket, bug fix or feature.