roster-skill-evolve

Implement approved Roster skill improvements with validation and human approval gates.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-skill-evolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster-skill-evolve
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-skill-evolve
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-skill-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of ungoverned, error-prone modifications to Roster pipeline skills and components by providing a structured, approval-gated workflow for implementing only the improvements explicitly approved by skill health checks.

Core Features & Use Cases

  • Proposal Processing: Handles 5 types of approved proposals: new skills, deterministic tools, skill adaptations, new dedicated agents, and workflow template promotions.
  • Governance Enforcement: Requires explicit human approval before and after every change, preventing unvetted modifications to critical pipeline components.
  • Validation & Coherence: Runs post-edit integrity checks and harness coherence validation to ensure all changes integrate cleanly with the existing Roster ecosystem.
  • Use Case: For example, if a skill health check identifies a recurring friction in the implement phase that can be resolved with a new bash script, this Skill will guide you through writing the script, patching the affected skill, and validating the harness before installation.

Quick Start

Use the roster-skill-evolve skill to implement the next approved improvement proposal from the latest skill health report, following all required validation and human gate steps.

Frequently Asked Questions about roster-skill-evolve

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

FAQPage Schema
How do I implement approved pipeline improvements from skill health checks?

To implement approved pipeline improvements from skill health checks, process the approved proposals and apply changes to skills, tools, agents, or workflow templates. The process requires explicit human approval before and after every modification to prevent unvetted changes.

What types of proposals can be processed for governed skill evolution?

Governed skill evolution handles five types of approved proposals: new skills, deterministic tools, skill adaptations, new dedicated agents, and workflow template promotions. Each proposal type follows a structured, approval-gated workflow for safe implementation.

How do I validate agent skills and pipeline components after making changes?

Validate agent skills and pipeline components after changes by running post-edit integrity checks and harness coherence validation. These checks ensure all modifications integrate cleanly with the existing Roster ecosystem before final installation.

Do I need human approval to modify workflow templates in a governed pipeline?

Yes, human approval is required to modify workflow templates in a governed pipeline. Governance enforcement mandates explicit human approval before and after every change, preventing unvetted modifications to critical pipeline components.

When should I use an approval-gated workflow for skill adaptations?

Use an approval-gated workflow for skill adaptations when changes to agent skills and pipeline components occur within governed software development workflows. This ensures post-edit validation and harness coherence checks are completed before installation.

Why does ungoverned skill modification cause errors in agent orchestration pipelines?

Ungoverned skill modification causes errors in agent orchestration pipelines because changes bypass post-edit integrity checks and harness coherence validation. Without structured, approval-gated workflows, unvetted modifications break critical pipeline component integration.