sdd-evidenceDiscover, build, verify, and optionally export (HTML, optional PDF) the evidence manifest of one SDD Composy task in evidence_required, routing it toward review_required. Use when acceptance evidence must be assembled or checked — 'juntar as evidências da task', 'gerar o relatório de evidências', 'v
sdd-executeImplement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'.
sdd-fleetLaunch, inspect, or tear down an isolated fleet of ready SDD Composy tasks: one branch and Git worktree per member, a bound LOOP, cmux/tmux/headless presentation, no automatic merge. Use to run several ready tasks in parallel — 'rodar várias tarefas em paralelo', 'lançar o fleet', 'fleet status', 't
sdd-initInitialize or resume the SDD Composy workspace of a repository: preview missing governance and OKF bundle files, apply only approved absent paths, persist the artifact language, and verify. Use when a project needs SDD set up or resumed — 'inicializar o SDD', 'configurar o workspace SDD', 'run init
sdd-loopRun a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a ta
sdd-mapProduce a deterministic, read-only evidence map of the repository for SDD Composy (languages, manifests, commands, modules, boundaries, staleness) and publish the context bundle only on request. Use before a PRD or TechSpec, or when the map is stale — 'mapear o repositório', 'atualizar o contexto do
sdd-prdCreate or revise the problem-first SDD Composy PRD (tasks/prd-SLUG/prd.md) with stable RF/CA identifiers, stopping at the human approval gate. Use when a user problem needs a product contract — 'criar o PRD', 'documento de requisitos', 'revisar o PRD do slug X', 'write the requirements for…'. Do NOT
sdd-qaIndependent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a
sdd-quickDeliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'q
sdd-reviewIndependent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'
sdd-statusRead-only consolidated snapshot of an SDD Composy workspace: lifecycle stage, task contracts, trace integrity, loops, fleets, and the next action, without changing any file. Use for 'em que pé está o SDD', 'status do fluxo', 'qual a próxima ação', 'where are we in the workflow'. Do NOT use for git,
sdd-storiesCreate, revise, or resolve applicability for SDD Composy user stories (US/SC) from an approved PRD and domain evidence, stopping at the human gate. Use after the PRD is approved — 'gerar as histórias de usuário', 'cenários de aceite', 'stories for prd-SLUG', 'is stories NOT_APPLICABLE here'. Do NOT
sdd-syncReconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and
sdd-tasksGenerate and safely advance the SDD Composy task projection from approved PRD, stories, and TechSpec: import contracts, list/next/show, and guarded start/block/transition/verify. Use when work must be decomposed or a task's state inspected or moved — 'quebrar a spec em tarefas', 'listar as tarefas',
sdd-techspecCreate or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnic
sdd-traceInspect, rebuild, or verify the append-only SDD Composy semantic trace (events.jsonl) and its derived projection (trace.json). Use for 'o que aconteceu nessa task', 'histórico do fluxo', 'verificar o trace', 'rebuild the trace projection'. Do NOT use for a status overview (sdd-status), evidence mani
sdd-verifyAdversarial verification of one SDD Composy task in verify_required: reproduce every claim with fresh commands, build the truth table, refute stale evidence, and produce the verdict that gates complete. Use when review is done and the task claims to be finished — 'verificar a TASK-003', 'a task está