start-epic

You prevent premature epic activation by enforcing architecture proposal review and explicit approval gates. The workflow validates epic states like proposal-pending, requiring governance checks before transitioning the epic to active.

An architecture proposal gate controls epic progress by loading the proposal, demanding user approval, and only activating the epic after the formal gate is passed. This prevents misalignment and duplicated effort.

Start the approval and activation workflow by providing the epic name. The system orchestrates loading the architecture proposal, guides you through the review, and records approval and activation in the project state log.

Yes, you can skip or revise architecture proposals during the review process. The workflow guides users through proposal evaluation, allowing changes or skipping when appropriate before seeking explicit activation approval.

The state machine enforces state checks for epic states like needs-architecture-proposal, preventing invalid transitions. It creates architecture directories when needed and records approval and activation in the project state and activity log.

After architecture approval, the system merges the target architecture for the epic and propagates required changes to downstream skills. This ensures consistency across the workflow and prevents duplicated effort.