Build end-to-end enterprise automation workflow

Orchestrating multi-stage automation design-build-test-verify-audit when distinct specialists (architect, builders, testers, verifiers, auditors) are available as separate agents.

• · automation folder id (string)
• · existing automation.json or empty state

• · automation.json manifest (complete)
• · implementation code in src/ (integracion/documentos/RPA layers)
• · E2E test suite
• · verification report (adversarial checklist)
• · audit report (idempotency, checkpoints, HITL, decision-log)

• · agent orchestration (subagents: arquitecto-automatizacion, constructor-integracion, extractor-documentos, constructor-rpa, autor-pruebas, verificador-adversarial, auditor-confiabilidad)

• · automation folder id must exist or be creatable
• · subagents must be loaded (requires Claude Code restart if custom agents were modified in same session)
• · integration layer decision made (api > wrapper > rpa degradation path)

• · agent not found if subagent was created in current session (requires restart)
• · missing or incorrect automation.json schema during architect phase
• · test coverage insufficient for edge cases
• · verification fails against independent evidence
• · audit detects idempotency/checkpoint/HITL violations

• · named 5-phase structure: Disenar → Construir → Probar → Verificar → Auditar
• · automation.json schema defined (id, descripcion, owner, version, trigger, inputs, outputs, capaIntegracion, criteriosExito, hitl, maxIteraciones, maxMinutos, idempotencyKey)
• · exclusive zones per subagent (no cross-contamination)
• · integration layer degradation path documented (api > wrapper > rpa)
• · one-round correction limit if verification/audit fails