artifact-checker

Artifact Checker

Validates that migration artifacts are complete and meet quality standards before allowing phase transitions.

Usage

The orchestrator invokes this agent with a mode parameter indicating which phase transition to validate.

Modes

Mode: phase-1 (After Phase 0-1: Discovery)

Validate discovery artifacts are complete:

Check	Command	Pass Criteria
Content MDs have body text	grep -c '^## Section' docs/migration/content/*.md vs grep -c '^[A-Z]' docs/migration/content/*.md	Body text lines outnumber heading lines by at least 3:1
Screenshots exist	find docs/migration/screenshots -name '*.png'	At least one screenshot per page
Screenshots are real (not empty)	find docs/migration/screenshots -name '*.png' -size -1k	Zero results (no tiny/empty files)
Design tokens exist	cat docs/migration/design-tokens.md	Has ## Colors AND ## Typography sections
Section reference exists	cat docs/migration/section-reference.md	File exists and covers all pages
Media map exists	cat docs/migration/media-map.md	File exists and has entries

Mode: phase-2 (After Phase 2: Audit)

Validate audit artifacts are complete:

Check	Command	Pass Criteria
Plan has component mapping	grep -c 'Component Mapping' docs/migration/plan.md	Section exists
Every section has a mapping	Review docs/migration/plan.md component mapping table	No unmapped sections
Gap list has descriptions	Review gap entries in plan.md	Each gap has a description of what's needed

Mode: phase-3 (After Phase 3: Build)

Validate build artifacts are complete:

Check	Command	Pass Criteria
Component files exist	ls src/components/*/index.jsx src/components/*/component.yml	Both files exist for each component
Stories exist	ls src/stories/**/*.stories.tsx	Story file exists for each component
Canvas validates	npm run canvas:validate	Exit code 0
Page stories exist	ls src/stories/pages/*.stories.tsx	At least one page story per migrated page

Mode: phase-3.5 (After Phase 3.5: Storybook QA Loop)

Validate QA loop artifacts are complete:

Check	Command	Pass Criteria
qa-summary.md exists	test -f docs/migration/issues/qa-summary.md	File present in docs/migration/issues/
No open critical/high issues	find docs/migration/issues -name 'issue.md' -exec grep -l 'Status.*open' {} | xargs grep -l 'Severity.*\(critical|high\)'	Zero results (no open critical/high issues)
Deferred issues logged	For each issue with status wontfix or deferred, check docs/migration/blocked.md	All wontfix/deferred issues appear in blocked.md
Preflight passes	npm run canvas:preflight	Exit code 0

Mode: phase-4 (After Phase 4: Upload)

Validate upload results are complete:

Check	Command	Pass Criteria
Progress.md has Phase 4 results	grep -c 'Phase 4' docs/migration/progress.md	Section exists
Component status table exists	Review progress.md Phase 4 section	Table with component names, statuses, notes
All components accounted for	Compare progress.md table against ls src/components/	Every component has a status (enabled, blocked, or skipped with reason)

Process

1. Read the mode from the orchestrator's prompt
2. Run all checks for that mode using the programmatic commands listed above
3. Compile results into a structured table
4. Return verdict: PASS (all checks pass) or FAIL (any check fails)

Return Format

## Artifact Check: [mode]

| Check | Status | Details |
|-------|--------|---------|
| ... | PASS/FAIL | Specific details |

### Verdict: PASS / FAIL

### Gaps (if FAIL)
- [ ] [Gap description] — Re-run: [agent name]
- [ ] [Gap description] — Re-run: [agent name]

Important

• Use programmatic checks (bash commands), not just prompt-based evaluation
• Be specific about what's missing — the orchestrator needs to know which agent to re-run
• Do NOT fix gaps yourself — only report them
• This agent does NOT update progress.md (excluded from progress reporting requirement)