Back to list
deepeshBodh

validation-plan-artifacts

by deepeshBodh

SPEC-first multi-agent framework for Claude Code.

7🍴 0📅 Jan 24, 2026

SKILL.md


name: validation-plan-artifacts description: This skill should be used when the user asks to "review research", "review data model", "review contracts", or mentions "plan quality", "phase review", or "design gaps". Provides phase-specific review criteria for planning artifacts with issue classification.

Reviewing Plan Artifacts

Purpose

Find gaps in planning artifacts and generate issues that need resolution before proceeding to the next phase. Focus on design completeness and quality, not implementation details. This skill provides phase-specific review criteria for the Devil's Advocate.

Review Focus by Phase

Each phase has specific checks to execute. The checks identify Critical, Important, and Minor issues.

PhaseFocus AreaKey Checks
A0Codebase DiscoveryCoverage, entity/endpoint detection, collision assessment
B0ResearchMarker resolution, alternatives, rationale quality
B1Data ModelEntity coverage, relationships, PII identification
B2ContractsEndpoint coverage, schemas, error handling
B3Cross-ArtifactAlignment, consistency, traceability

See PHASE-CHECKLISTS.md for detailed phase-specific checklists and key questions.

Issue Classification

Issues are classified by severity to determine appropriate action:

SeverityDefinitionAction
CriticalBlocks progress; must resolveReturn to responsible agent
ImportantSignificant gap; should resolveFlag for this iteration
MinorPolish item; can deferNote for later

See ISSUE-TEMPLATES.md for severity classification rules, issue documentation formats, and report templates.

Review Process

Step 1: Gather Context

Read and understand:

  • The artifact being reviewed
  • The spec requirements it should satisfy
  • Previous artifacts (for consistency checks)
  • Constitution principles (for compliance)

Step 2: Execute Checks

For each check in the phase-specific checklist:

  1. Ask the question
  2. Look for evidence in the artifact
  3. If issue found, classify severity
  4. Document the issue

Step 3: Cross-Reference

  • Check traceability (can trace requirement -> artifact)
  • Check consistency (artifacts agree with each other)
  • Check completeness (nothing obviously missing)

Step 4: Generate Report

  • Classify verdict based on issues found
  • Document all issues with evidence
  • Provide specific, actionable suggestions
  • Acknowledge what was done well

Incremental Review Mode

For phases after the first artifact (data-model, contracts), use incremental review to optimize time while preserving rigor.

Full Review (New Artifact Only)

  • Execute ALL phase-specific checks from PHASE-CHECKLISTS.md
  • Document issues with full evidence
  • This is your primary focus—no shortcuts here

Consistency Check (Previous Artifacts)

  • Use the cross-artifact checklist at ${CLAUDE_PLUGIN_ROOT}/templates/cross-artifact-checklist.md
  • Do NOT re-read previous artifacts in full
  • Spot-check: entity names, requirement IDs, decision references
  • Flag only inconsistencies between artifacts
  • Time budget: 1-2 minutes per previous artifact

When to Escalate to Full Re-Review

  • If 2+ consistency issues found → re-read that specific artifact
  • If contradictions detected → flag for supervisor
  • If unsure → note uncertainty in report, recommend targeted review

Report Format (Incremental Mode)

## Review Summary

| Aspect | Status |
|--------|--------|
| **New Artifact** | {artifact} - FULL REVIEW |
| **Previous Artifacts** | CONSISTENCY CHECK ONLY |

## New Artifact Issues

{Full issue documentation with evidence}

## Cross-Artifact Consistency

| Check | Status | Notes |
|-------|--------|-------|
| Entity names | Pass/Fail | {any mismatches} |
| Requirement IDs | Pass/Fail | {any gaps} |
| Decision alignment | Pass/Fail | {any contradictions} |

## Verdict

{ready / needs-revision / critical-gaps}

Phase Application

PhaseFull ReviewConsistency Check
B0 (Research)research.md— (first artifact)
B1 (Data Model)data-model.mdresearch.md (1-2 min)
B2 (Contracts)contracts/, quickstart.mdresearch.md + data-model.md (2-3 min)

Verdict Criteria

VerdictCriteria
readyZero Critical, zero Important issues
needs-revision1-3 Important issues, fixable in one iteration
critical-gaps1+ Critical or 4+ Important issues

Quality Checklist

Before finalizing review, verify:

  • All phase-specific checks executed
  • Issues properly classified by severity
  • Evidence cited for each issue
  • Suggested fixes are actionable
  • Verdict matches issue severity
  • Cross-artifact concerns noted
  • Strengths acknowledged

Score

Total Score

65/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon