Validate workflow documents against templates. Use when verifying PRD, execution plan, or user story files before HITL approval - checks required frontmatter fields and sections against templates.
Validates workflow documents (PRD, execution plans, user stories) against required frontmatter fields and section templates before HITL approval. Triggers on document path and type to catch missing critical sections and malformed metadata.
/plugin marketplace add metasaver/claude-marketplace/plugin install core-claude-plugin@metasaver-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Validate workflow documents against template requirements
Trigger: Called by reviewer agent before HITL approval
Input: Document path, document type (prd | execution-plan | user-story)
Output: {valid, document_type, issues[], checked_fields[], checked_sections[]}
| Pattern | Document Type |
|---|---|
project_id in frontmatter | PRD |
total_stories in frontmatter | Execution Plan |
story_id in frontmatter | User Story |
--- markers)Run type-specific validation (see checklists below).
Frontmatter: project_id, title, version, status, owner, created, updated
Sections: ## 1. Executive Summary, ## 2. Problem Statement, ## 3. Solution Overview, ## 4. Requirements, ## 5. Scope, ## 6. Epic Summary, ## 7. Success Criteria
Frontmatter: project_id, title, status, total_stories, total_complexity, total_waves, owner, created, updated
Sections: ## Summary, ## Wave Strategy Overview, ## User Stories Index, ## Wave N: (at least one)
Frontmatter: story_id, epic_id, title, status, complexity, wave, agent, dependencies, created, updated
Sections: ## User Story, ## Acceptance Criteria, ## Technical Details, ## Definition of Done
| Issue Type | Description | Severity |
|---|---|---|
missing_field | Required frontmatter field absent | CRITICAL |
missing_section | Required markdown section absent | CRITICAL |
invalid_format | Field value format incorrect | WARNING |
empty_section | Section exists but empty | WARNING |
{
"valid": true|false,
"document_type": "prd|execution-plan|user-story",
"issues": [{"type": "...", "field|section": "...", "message": "..."}],
"checked_fields": [{"field": "...", "status": "pass|fail"}],
"checked_sections": [{"section": "...", "status": "pass|fail"}]
}
Called by: reviewer agent, hitl-approval skill, /ms command
References:
../prd-creation/templates/prd-template.md../execution-plan-creation/templates/execution-plan-template.md../user-story-creation/templates/user-story-template.mdNext: Valid -> HITL approval; Invalid -> return to authoring agent
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.