gov-review-gate-management

Auditable review gates are created by generating HUS-* review stories in the execution-plan backlog with structured frontmatter and linked artifacts. This ensures explicit human decisions and traceable records govern project gates across architecture, planning, implementation, and release phases.

A governance gate is a workflow stage requiring explicit human approval, change requests, or gate decisions. You need it when work must only proceed with authorization, ensuring decisions are traceable across phases like architecture, planning, implementation, and release.

Human decisions such as approve, request-changes, and defer are recorded through provided scripts that update the gate state and backlog. This maintains explicit gate state so downstream automation and teams know the next steps.

Yes, managing review stories requires the project_state and generate_ids dependencies to properly generate HUS-* stories and maintain backlog state updates across the governance workflow.

The best way to automate governance gating is using a skill that creates structured review stories with frontmatter, records human decisions, and maintains explicit gate state. This provides repeatable guidance and traceable records across architecture, planning, implementation, and release phases.