Major Improvement

Creates versioned plans, canonical rules, and enforcement entries from improvement ideas.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill major-improvement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Major Improvement
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/major-improvement
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill major-improvement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn big org-wide improvement ideas into versioned plan artifacts, persistent rules, and red/yellow/green enforcement entries. Mandatory prior-context discovery. No loss of iteration history.

Core Features & Use Cases

  • Create a versioned plan artifact to capture history and decisions for large initiatives.
  • Define a canonical rule entry to enforce durable standards.
  • Establish red/yellow/green enforcement definitions to monitor progress.

Quick Start

Convert an improvement idea into a versioned plan, canonical rules, enforcement criteria, and a registry entry.

Frequently Asked Questions about Major Improvement

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

FAQPage Schema
How do I turn organization-wide improvement ideas into structured plans and rules?

To convert improvement ideas into structured plans and rules, you need a system that generates versioned plan artifacts and canonical rule entries. This approach captures iteration history and establishes durable standards across multiple teams.

What is prior-context discovery for major improvement initiatives?

Prior-context discovery is a mandatory prerequisite for major improvement initiatives that ensures existing organizational context is captured before generating new versioned plans, canonical rules, and enforcement definitions.

How do I set up red, yellow, and green enforcement definitions for governance rules?

Setting up red, yellow, green enforcement definitions involves creating canonical rule entries with measurable enforcement criteria. These definitions monitor progress and rule compliance across large organizations through a central rule registry.

Can I track version history and decisions for large-scale governance plans?

Yes, versioned plan artifacts track iteration history and decisions for large-scale governance plans. This prevents loss of iteration history and maintains a record of how major improvement initiatives evolve over time.

Does this approach require a central rule registry for versioned plans?

Yes, the approach integrates with a central rule registry to manage canonical rule entries and enforcement definitions. This centralization ensures durable standards are maintained and accessible across multiple teams in large organizations.

When should I not use automated rule enforcement for improvement initiatives?

Automated rule enforcement for improvement initiatives is not suitable for small-scale or informal changes that do not require durable standards or versioned artifacts. It is designed for large organizations needing structured governance and measurable enforcement.