Use when a task needs to be executed through the full development pipeline — classification, delegation, QA, user testing, and learning propagation. Triggers on /task command or when a user describes implementation work in an already-scaffolded project. Do NOT use for questions, wiki updates, or simple file edits.
Use before executing the first operational task of a phase and any Complex task. Runs a structured design dialogue — questions one at a time, 2-3 approaches with trade-offs, sectioned design approval — before any code is written. The approved design may revise scaffold-era rules. Triggered by the Cortex (Step 3b) or…
Use after QA passes to simulate end-user testing with diverse profiles. Triggered by Cortex for tasks that impact UI, user flows, or user-facing text. Do NOT use for backend-only or infrastructure tasks. Also triggers on "test with users", "user simulation", "persona test", or "UX validation".
Use to log every operation in the synaptic pipeline. Called by Cortex, Synapse, Persona-Lab, and QA Agent at each step. Maintains daily pipeline logs and a separate error log for fast debugging. Do NOT use directly — other skills call this automatically.
Use when starting ANY new project from a user brief. Generates the complete project structure automatically — CLAUDE.md hub, Karpathy-style wiki (12 core pages + on-demand), vertical skills, guardrails, handoff protocol, design spec, and implementation plan. Also triggers on "new project", "setup project"…
Use after a task completes to propagate learning across connected skills. Triggered by Cortex at the end of every successful task pipeline. Also triggers on "propagate learning", "update skills", "synapse", or when skills need cross-pollination after discovering shared patterns or errors.