Validates Requirements Phase completion before advancing to Design Phase. Checks business requirements document for completeness, quality gate compliance, and readiness for design work.
Validates business requirements documents for completeness and quality before advancing to design phase. Automatically triggered when checking if requirements are ready for design work, scoring structure, content quality, and WitchCityRope-specific considerations against work-type quality gates.
/plugin marketplace add DarkMonkDev/WitchCityRope/plugin install darkmonkdev-witchcityrope-agents@DarkMonkDev/WitchCityRopeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Automate validation of Requirements Phase completion before advancing to Design Phase.
When to Use: When orchestrator or agents need to verify requirements are ready for design work.
Executable Script: execute.sh
# Basic usage with requirements document path
bash .claude/skills/phase-1-validator/execute.sh <requirements-document-path>
# With work type specification
bash .claude/skills/phase-1-validator/execute.sh <path> <work-type>
# With custom quality gate threshold
bash .claude/skills/phase-1-validator/execute.sh <path> Feature 95
# Examples:
bash .claude/skills/phase-1-validator/execute.sh docs/functional-areas/events/new-work/business-requirements.md
bash .claude/skills/phase-1-validator/execute.sh docs/functional-areas/checkin/new-work/business-requirements.md Bug 80
Parameters:
requirements-document-path: Path to business-requirements.md filework-type: (optional) Feature|Bug|Hotfix|Docs|Refactor (default: Feature)required-percentage: (optional) Override quality gate thresholdScript validates:
Exit codes:
Use the phase-1-validator skill to check if requirements are ready for design
# Find requirements document
REQ_DOC=$(find docs/functional-areas -name "business-requirements.md" -path "*/new-work/*" -type f | tail -1)
# Run validation
bash .claude/skills/phase-1-validator.md "$REQ_DOC"
The orchestrator should automatically invoke this skill:
Solution: Business requirements agent should add specific, measurable metrics like:
Solution: User stories should be specific to WitchCityRope context:
Solution: Every feature should address safety implications:
The skill should output a validation report:
{
"phase": "requirements",
"status": "pass|fail",
"score": 23,
"maxScore": 25,
"percentage": 92,
"requiredPercentage": 95,
"missingItems": [
"Mobile experience not mentioned",
"Only 2 user stories (need 3+)"
],
"recommendations": [
"Add user story for mobile registration flow",
"Add user story for admin monitoring"
],
"readyForNextPhase": true
}
This skill enforces the quality gate thresholds by work type:
Initial Context: Show quick checklist On Request: Show full validation script On Failure: Show specific missing items and recommendations On Pass: Show concise summary only
Remember: This skill automates validation, it doesn't replace the business-requirements agent's judgment. If validation fails, the orchestrator should loop back to business-requirements agent for completion.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.