End-to-end feature pipeline with ONE human gate before code — Research (grilling rounds + parallel code scouts; a raw concept is stress-tested before convergence), then autonomous Plan → Implement → Review — top-tier planning over mapped context, cheap…
Spec-driven feature work in 4 phases — Specify, Design, Tasks, Execute — sized by complexity; atomic tasks and commits, Execute delegated to workers in waves plus an independent Verifier. Triggers on "specify/discuss feature", "design", "tasks", "implement",…
Expert, skeptical business analyst for a business / startup / product idea. Grills the user about the idea (one round of pointed questions at a time), then runs deep market research in the home country (default Brazil) and internationally — TAM/SAM/SOM,…
Write a crash course — a study document, like a short documentary — about a concept, either one registered as debt in `.learning/DEBT.md` (e.g. "/crash-course DEBT-007") or any topic the user names ("/crash-course event sourcing", "explain properly what this…
Register technical or cognitive debt about something AI implemented in the project, as a personal pending item in `.learning/DEBT.md`. Use whenever the user explicitly asks to record, log, note or flag a debt — "/debt", "log this as debt", "note this as tech…