governor

Enforce project tier constraints and audit scope for over-engineering.

412|45|Updated Feb 19, 2026

Search Tags:#project management #governance #scope #development methodology #over-engineering #tiering

Ready to run

npx skills add https://github.com/cwinvestments/memstack --skill governor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governor
Source: https://github.com/cwinvestments/memstack/tree/main/skills/governor
Command: npx skills add https://github.com/cwinvestments/memstack --skill governor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents over-engineering by enforcing project tier constraints, ensuring that development effort is appropriately allocated and complexity is managed throughout the project lifecycle.

Core Features & Use Cases

Tier Enforcement: Assigns and enforces constraints based on project maturity (Prototype, MVP, Production).
Scope Auditing: Flags proposed work that exceeds current tier limitations.
Anti-Rationalization: Provides guidance to avoid common scope creep pitfalls.
Use Case: When starting a new project, the Governor skill will help define whether it should be a quick prototype with minimal features or a more robust MVP, guiding the developer on what is appropriate to build at each stage.

Quick Start

Use the governor skill to check the project tier constraints for a new project.

Frequently Asked Questions about governor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent over-engineering during project development?▼

To prevent over-engineering, enforce project tier constraints using a 3-tier system (Prototype, MVP, Production) that audits scope and flags violations. This approach ensures development effort is appropriately allocated and complexity is managed throughout the lifecycle.

What is project tiering in development methodology?▼

Project tiering assigns constraints based on project maturity, categorizing work into Prototype, MVP, or Production phases. It guides developers on appropriate complexity levels for each stage, ensuring minimal features for prototypes and robust builds for production.

How do I audit project scope for creep and complexity violations?▼

Audit project scope by enforcing tier limitations that flag proposed work exceeding current maturity constraints. This scope auditing process provides anti-rationalization guidance to avoid common pitfalls and prevent development effort misallocation.

When should I use a prototype tier versus an MVP tier?▼

Use the prototype tier for new projects requiring quick validation with minimal features, and transition to the MVP tier when a more robust build is needed. Tier enforcement defines appropriate development effort allocation based on project maturity.

Can this governance approach work for existing production projects?▼

Yes, the governance approach applies to production projects by enforcing tier-appropriate complexity constraints and auditing scope. It provides anti-pattern guidance for each phase, ensuring development effort remains appropriately allocated even at production maturity.