What problem does it solve? Long engineering prompts pasted into a skill lose effectiveness after a few turns because the instructions sink in context and vanish after compaction. This Skill replaces prompt text with on-disk state: the cycle lives in .engine/estado.json and a UserPromptSubmit hook re-injects a compact status card every turn, so the engineering mode persists for the whole session. ## Core Features & Use Cases - Phase cycle with enforced transitions: DESCOBERTA → ANÁLISE → EVOLUÇÃO → PLANO → gate → BUILD ⇄ TESTE → REVISÃO → DOC → ENTREGA, with out-of-graph transitions refused by the CLI. - Role-based subagents: nine roles (descobridor, cartografo, arquiteto, designer, implementador, testador, revisor, sentinela, documentador) dispatched per phase, where only the implementador has broad write access and the revisor structurally cannot fix code silently. - Risk gates and plan gate: the risk hook blocks dangerous actions with [R<n>] codes requiring explicit user confirmation, and the plan gate pauses for user approval of architecture and stack decisions. - Use Case: Start a full end-to-end feature build by running /engine add user authentication, letting the motor drive discovery, planning with an approval gate, implementation, testing, review, and documentation while state survives context compaction. ## Quick Start Ask the AI to run /engine followed by a one-sentence objective, such as "/engine build a REST API for task management", to start the persistent engineering cycle.
