yao-meta-skill/WORLD_CLASS_PLAN.md

World-Class Plan

yao-meta-skill should not compete by becoming the largest meta-skill. It should compete by becoming the most rigorous lightweight system for creating, evaluating, packaging, and governing reusable agent skills.

Positioning

The intended advantage is:

• lighter than heavyweight skill-creation systems
• more evaluation-aware than purely structural systems
• more trustworthy than ambition-heavy skill factories
• stronger at lifecycle governance than typical skill creators

Scoring Targets

• Trigger design: 9.4+
• Methodology depth: 9.5+
• Executability: 9.3+
• Evaluation and iteration: 9.5+
• Engineering support: 9.4+
• Cross-platform packaging: 9.2+
• Simplicity: 9.0+

Strategic Pillars

1. Lightweight By Default

Protect SKILL.md from bloat and push detail into the right place.

2. Eval Before Expansion

Validate routing and boundaries before making the skill bigger.

3. Explicit Boundary Design

Make scope, exclusions, and near-neighbor behavior legible.

4. Evidence Over Claims

Expose regressions, family results, failure modes, and change history.

5. Governance As Product

Treat important skills as maintained assets with owners, cadence, and lifecycle state.

Implementation Sequence

Phase 1

• resource boundary spec
• governance spec
• quality checks wired into validation
• visible regression reporting

Phase 2

• thicker benchmark suites
• heavier production examples
• versioned regression history
• maturity scoring and certification ideas

Phase 3

• stronger adapter conformance
• broader external benchmark evidence
• deeper library governance workflows

Four-Dimension Sprint

The current sprint is aimed at the four dimensions that most directly determine whether this project can challenge first-tier skill-creation systems.

Trigger

• route confusion matrix
• contrastive route testing across sibling skills
• mutation-based and adversarial route families
• judge-backed blind eval so blind acceptance does not depend on one scorer

Method

• promotion policy
• explicit gate-selection doctrine
• non-skill decision rules for when packaging should not happen
• formal skill engineering method and archetype taxonomy

Execution

• one-command route scorecard generation
• iteration ledger that shows current route quality and optimization evidence
• validation hooks that fail on route ambiguity or route theft

Iteration

• blind and adversarial drift history
• promotion rules for visible holdout, blind holdout, adversarial holdout, and route confusion
• versioned scorecards that show why a route should or should not be promoted

Acceptance Criteria

The project is only world-class if it remains:

• compact at the entrypoint
• reproducible in evaluation
• explicit in packaging limits
• auditable in governance
• credible through public evidence