engineering-principlesPrincipios canonicos de engenharia (SOLID, KISS, DRY, YAGNI, SSOT, Clean Architecture, fail-fast, defensive-at-boundaries). Fonte de regra default quando uma decisao tecnica nao esta coberta pela spec do workflow. Carregada por TODOS os 50 cargos como ultima linha de defesa antes de escalar ambiguid
pipeline-orchestrator-adversarialProtocolo de revisao adversarial (zero-context) com checklists de security, architecture e quality. Usado pelos cargos adversarial-* e final-adversarial-orchestrator.
pipeline-orchestrator-audit-methodMetodo de auditoria de codebase em 4 fases — Intake (inventory), Domain Analyzer (arquitetura + SSOT), Compliance Checker (integrity + security), Risk Matrix (priorizacao + backlog). Usado pelos cargos audit-*.
pipeline-orchestrator-bugfix-methodMetodo cientifico para bug fix — Diagnostic (terrain + hypothesis ranking) → Root Cause (evidence chain) → Fix (TDD via regressao) → Regression Test (suite + adjacent breakage). Usado pelos cargos bugfix-*.
pipeline-orchestrator-classificationClassificacao de tipo de tarefa (Feature, Bug Fix, User Story, Spec, UX, Audit, Adversarial Review) e nivel de complexidade (SIMPLES, MEDIA, COMPLEXA), com regras de roteamento. Usada por task-orchestrator e information-gate.
pipeline-orchestrator-contractsContratos de comunicacao adaptados (GATE_REQUEST, DISPATCH_REQUEST, ORCHESTRATOR_DECISION, etc.) do pipeline-orchestrator original para o modelo Paperclip+Codex (assincrono, ticket-based, comment-driven).
pipeline-orchestrator-iron-lawsIron Laws inalteradas do pipeline-orchestrator original (TDD obrigatorio, ask-first em ambiguidade, self-review, stop rule, evidence-based decisions). Carregada por todos os 50 cargos.
pipeline-orchestrator-spec-protocolProtocolo de spec lifecycle (format-gate, content-review, post-impl-validator) com formato EARS e regras de aceitacao. Usado pelos cargos spec-*.
pipeline-orchestrator-tddImplementacao de TDD (Test-Driven Development) com fase RED obrigatoria antes de GREEN. Usado por todos os cargos executor que escrevem codigo.
pipeline-orchestrator-ux-methodMetodo de UX review — persona matrix + jornadas + WCAG 2.1 AA accessibility + consolidacao com matriz de prioridade. Usado pelos cargos ux-*.
pipeline-orchestrator-vsaVertical Slice Architecture para Feature/User Story pipelines — quebrar feature em slices verticais end-to-end com BDD Gherkin. Usada pelos cargos feature-*.
audit-heavyPrescriptive 9-step audit workflow for COMPLEXA audits (full system, multi-axis, regulatory, security-sensitive). Imported from Pulsar audit workflow per spec §22. Use when audit complexity is heavy or when audit-light auto-escalates at its scope gate. REPORT-ONLY by Iron Law — no code modification
audit-lightPrescriptive 9-step audit workflow for SIMPLES/MEDIA audits (1 area, 1 depth level, single-axis or narrow scope). Imported from Pulsar audit workflow per spec §22. Use when audit complexity is light. REPORT-ONLY by Iron Law — no code modification under any circumstance. Same 9-step structure as audi
auditAudit shortcut — skips task-orchestrator type-classification by pre-fixing task_type=Audit. Same pipeline machinery as /pipeline-orchestrator:pipeline (information-gate, design-interrogator, plan-architect, executor-controller, sanity, Pa de Cal). Invoked manually via `/pipeline-orchestrator:audit [
bugfix-heavyPrescriptive 11-step bug fix workflow for COMPLEXA bugs and production incidents (cross-cutting concerns, persistence, concurrency, multi-user impact, business rules). Imported from Pulsar bugfix workflow per spec §21. Use when complexity classification is heavy or when bugfix-light auto-escalates a
bugfix-lightbugfixfeature-heavyfeature-lightfeaturemeasure-paperclip-fidelitypipelinerefactor-heavyrefactor-lightrefactorreviewspec-audit-onlyspec-designspec-heavyspec-initspec-lightspec-requirementsspec-reviewspec-tasksspecunblockuser-story-heavyuser-story-lightuser-storyux-sim-heavyux-sim-lightux-simvalidate-designvalidate-gapverify-completion