critic-minimality

Flag excessive scope in change management contracts during verification.

3|Updated May 20, 2026

Search Tags:#code quality #scope creep #change management #developer tooling #contract verification

Ready to run

npx skills add https://github.com/iampawan/Manifest --skill critic-minimality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: critic-minimality
Source: https://github.com/iampawan/Manifest/tree/main/skills/critic-minimality
Command: npx skills add https://github.com/iampawan/Manifest --skill critic-minimality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents overreach in feature development, ensuring that changes remain aligned with their original intent and avoid unnecessary complexity.

Core Features & Use Cases

Flag Excessive Scope: Identify and flag changes that exceed the required scope, such as new analytics or shadow observations that aren't needed for a bug fix.
Optimize Contract Verification: Act as a primary guard for changeType:bug-fix, providing insights to developers to minimize the risk of feature creep.
Advisory Feedback: Offer findings at a warning level, suggesting improvements rather than blocking changes outright.

Quick Start

Invoke the critic-minimality skill within the contract-verify command to review the contract and identify potential over-scoped elements.

Frequently Asked Questions about critic-minimality

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

FAQPage Schema

How do I prevent scope creep in change management and keep bug fixes focused?▼

To prevent scope creep in change management, you need a verification workflow that flags excessive scope in development contracts. This skill identifies unnecessary additions and provides advisory warnings to ensure changes remain aligned with original goals.

How does contract verification identify over-scoped changes in a bug fix?▼

Contract verification identifies over-scoped changes by evaluating change management contracts against a set of minimality rules. It acts as a primary guard for bug fixes, flagging unnecessary features like new analytics or shadow observations that exceed required scope.

What is the best way to flag unnecessary features during code review?▼

The best way to flag unnecessary features is to use an automated minimality check within your verification workflow. It evaluates change contracts and generates warning-level findings to suggest improvements rather than blocking changes outright.

Does this minimality check block commits with excessive scope or just provide warnings?▼

This minimality check provides advisory feedback at a warning level rather than blocking commits outright. It offers insights to developers to minimize the risk of feature creep, suggesting improvements while allowing the change process to continue.

When do I need to use a minimality check for change management?▼

You need a minimality check when managing change contracts, especially for bug fixes where scope creep is a risk. It ensures changes are justified by their goals and prevents overreach in feature development by flagging unjustified complexity.

Can I use this scope verification tool without additional dependencies?▼

Yes, you can use this scope verification tool without additional dependencies. It operates standalone with internal scripts and references to analyze change contracts and flag excessive scope directly within your workflow.