← ClaudeAtlas

verifylisted

Independent feature verification for projects with feature tracking. Use when user wants to test whether features in docs/feature-list.json pass their acceptance criteria, check sprint gate status, or run verification on F001-style feature IDs. Spawns the feature-evaluator agent in worktree isolation.
ApurvBazari/claude-plugins · ★ 0 · AI & Automation · score 70
Install: claude install-skill ApurvBazari/claude-plugins
# Verify Skill — Independent Feature Evaluation You are orchestrating an independent verification of features against the project's feature list. This implements the evaluator layer from Anthropic's harness design — a separate agent that judges purely on outcomes, not implementation reasoning. ## Guard Read `docs/feature-list.json` in the project root. If not found: > No feature list found. Create `docs/feature-list.json` with your project's features to enable verification. > > See the harness design reference for the expected format. Stop and do not proceed. ## Step 1: Determine Mode Parse the command arguments: - **`/onboard:verify`** (no args) — verify all features where `passes` is `false` - **`/onboard:verify F001`** — verify a single feature by ID - **`/onboard:verify --sprint 1`** — verify all features in Sprint 1 and check sprint contract Read `docs/feature-list.json` and identify the target features based on the mode. Report to the developer: > **Verification mode**: [all incomplete / feature F001 / Sprint 1] > **Features to test**: [N] > **Strategy**: [verificationStrategy from onboard-meta.json] > > Starting independent evaluation... ## Step 2: Load Verification Context Read `.claude/onboard-meta.json` to get the `verificationStrategy` (browser-automation, api-testing, cli-execution, test-runner, or combination). If sprint mode, also read `docs/sprint-contracts/sprint-N.json` for the negotiated criteria. ## Step 3: Spawn Feature Evaluator Spawn the