Claude Skills
CollectionsCompareWorkflowsNominate
Sign inSign up
© 2026 Curated Agent Skills·Learn more about Agent Skills
Back to repository

validation-plan-artifacts

verified

This skill MUST be invoked when the user says "review research", "review data model", "review contracts", "plan quality", "phase review", or "design gaps". SHOULD also invoke when user mentions "artifact review" or "planning validation".

View on GitHub

Marketplace

humaninloop-plugins

deepeshBodh/human-in-loop

Plugin

humaninloop

Repository

deepeshBodh/human-in-loop
15stars

plugins/humaninloop/skills/validation-plan-artifacts/SKILL.md

Last Verified

February 5, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/deepeshBodh/human-in-loop/blob/main/plugins/humaninloop/skills/validation-plan-artifacts/SKILL.md -a claude-code --skill validation-plan-artifacts

Installation paths:

Claude
.claude/skills/validation-plan-artifacts/
Powered by add-skill CLI

Instructions

# Reviewing Plan Artifacts

## Overview

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.

## When to Use

- Reviewing research.md after B0 phase completion
- Reviewing data-model.md after B1 phase completion
- Reviewing contracts/ after B2 phase completion
- Validating cross-artifact consistency before task generation
- When plan architect requests artifact review
- Quality gate checks before phase transitions

## When NOT to Use

- **Implementation code review** - Use code review tools instead
- **Task artifact review** - Use `humaninloop:validation-task-artifacts` instead
- **Specification review** - Use `humaninloop:analysis-specifications` instead
- **Constitution review** - Use `humaninloop:validation-constitution` instead
- **During active drafting** - Wait for artifact completion before review

## Review Focus by Phase

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

| Phase | Focus Area | Key Checks |
|-------|------------|------------|
| A0 | Codebase Discovery | Coverage, entity/endpoint detection, collision assessment |
| B0 | Research | Marker resolution, alternatives, rationale quality |
| B1 | Data Model | Entity coverage, relationships, PII identification |
| B2 | Contracts | Endpoint coverage, schemas, error handling |
| B3 | Cross-Artifact | Alignment, consistency, traceability |

See [PHASE-CHECKLISTS.md](references/PHASE-CHECKLISTS.md) for detailed phase-specific checklists and key questions.

## Issue Classification

Issues are classified by severity to determine appropriate action:

| Severity | Definition | Action |
|----------|------------|--------|
| **Critical** | Blocks progress; must resolve | Return to responsible agent |
| **Important** | Significant gap; should resolve | Flag f

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
6189 chars