process-evolution

What problem does it solve?

Teams make ad-hoc changes to board statuses, transitions, and review gates that can create orphans, dead ends, infinite loops, or mismatches across human-readable and machine-readable configuration files; this Skill coordinates deliberate, repository-backed process changes and validates them before applying to avoid operational regressions and oversight gaps.

Core Features & Use Cases

• Cross-file consistency: Ensures PROCESS.md, botminter.yml, roles/*/ralph.yml, board-scanner dispatch tables, and status-workflow code stay synchronized.
• Graph validation: Runs orphan, dead-end, infinite-loop, role coverage, and board-scanner consistency checks before any change is applied.
• Governance and traceability: Records every accepted process change as a decision in agreements/decisions and prescribes workspace sync and restart steps to propagate changes.
• Use Case: Apply when a cos:todo requests adding/removing a status, changing transitions, introducing or removing review gates, updating auto-advance rules, or altering comment and label conventions.

Quick Start

Ask the skill to add a new status owned by an existing role, place it in the lifecycle after a named status, validate the resulting status graph, update PROCESS.md and botminter.yml, and record the accepted decision in agreements/decisions.