os-evolution-verifierlisted

Verifies that os-architect actually causes evolution — not just words. Dispatches os-architect in single-shot simulation mode for a given test scenario, then checks for real artifact presence (new files, HANDOFF_BLOCK, plan files). Reports PASS / FAIL with grep evidence. Accumulates results into a test report. Use after any changes to os-architect, os-evolution-planner, or improvement-intake-agent.
richfrem/agent-plugins-skills · ★ 6 · Data & Documents · score 77

Install: claude install-skill richfrem/agent-plugins-skills

## Overview After evolving os-architect or its downstream agents, you need proof that the changes actually work. This skill dispatches os-architect in single-shot simulation mode for each test scenario and verifies artifact presence — not by reading the transcript, but by checking that expected files exist or expected content appears in output. **Evolution is verified by artifact presence, not by transcript review.** --- ## Artifact Verification Table | Evolution Type | What to Check | |---|---| | Path C (Gap Fill) | `SKILL.md` present at expected path | | Path B (Update) | `tasks/todo/<slug>-plan.md` AND `tasks/todo/copilot_prompt_<slug>.md` written | | Path A+ (No-op) | No new files written; HANDOFF_BLOCK contains `STATUS: complete` | | Category 3 (Lab Setup) | `improvement/run-config.json` written AND HANDOFF_BLOCK emitted | | HANDOFF_BLOCK integrity | All 7 fields present: INTENT, TARGET, PATH, DISPATCH, STATUS, OUTPUTS, NEXT_ACTION | | Confidence model | Low confidence prompt → clarifying question appears before Phase 2 audit | | Evolution Integrity Gate | When logic in `plugins/` changes, `references/map-debt.md` or `evolution-log.md` is updated, or `Evolution-Check: none` is present | --- ## Procedure 1. **Resolve Test Inputs** — `all` scans `temp/os-evolution-verifier/scenarios/*.json`; a specific file is validated for required fields (`id`, `name`, `path`, `prompt`, `expected_artifact`, `artifact_check`). If none found, report that scenarios must be cre