What problem does it solve? Unstructured code changes often skip research, exceed scope, or ship without validation. This Skill enforces a mandatory council workflow so every feature, fix, dependency update, or refactor passes through defined review gates with human approval before delivery. ## Core Features & Use Cases - Five council seats: Researcher, Architect, Implementer, Validator, and Reviewer roles with strict read-only or edit permissions to separate concerns. - Gated workflow: A required sequence of intake, research, architecture approval, implementation, validation, review, and delivery, with explicit approve/revise/reject rules. - Decision records: Non-trivial changes are captured as structured council records in .github/council/ documenting scope, non-goals, validation plans, and findings. - Use Case: Before refactoring a Dynatrace app's data layer, run the council to map affected files, get architecture approval, implement within the approved scope, and validate against the recorded decision. ## Quick Start Ask the AI to run the change council for your next planned change, starting with an intake statement of the request, motivation, and non-goals.
