workflow-validate

Validate feature feasibility through structured analysis and rapid prototyping.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/specvital/infra --skill workflow-validate-specvital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-validate
Source: https://github.com/specvital/infra/tree/main/.claude/skills/workflow-validate
Command: npx skills add https://github.com/specvital/infra --skill workflow-validate-specvital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate the technical feasibility of proposed features by guiding structured analysis and rapid prototyping, reducing risk before heavy implementation.

Core Features & Use Cases

  • Structured validation flow: Check prerequisites, load analysis docs, select a validation method, execute, and document results.
  • Prototype-driven decision making: Create a minimal prototype under prototype/{feature-name}/ to prove core logic or interactions.
  • Dual-language documentation: Produce validation reports in English for agents and Korean for users, supporting transparent decision making.
  • Flexible validation methods: Support prototypes, UI/UX verification, TDD, library exploration, and research-based notes.
  • Evidence-based outcomes: Capture findings, constraints, and recommended next steps to guide planning.

Quick Start

Run the validation workflow for a candidate feature by analyzing docs/work/WORK-<task-name>/analysis.md and generating a prototype under prototype/{task-name}/, then document results in docs/work/WORK-<task-name>/validation.* (two languages).

Frequently Asked Questions about workflow-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate the technical feasibility of a proposed feature before full implementation?

To validate feature feasibility, this skill guides structured analysis and rapid prototyping under __prototype__/{feature-name}/, capturing evidence and decisions to reduce risk before heavy implementation.

What is the best way to choose between different technical approaches for a new feature?

Choosing between technical approaches is handled by applying structured validation methods like prototyping, TDD, or library exploration, then generating dual-language documentation of findings and recommended next steps.

How do I create a quick prototype to verify UI/UX interactions and core logic?

You can create a quick prototype to verify UI/UX interactions by following the structured validation flow to build a minimal proof-of-concept under the __prototype__/ directory.

Can I use Test-Driven Development to explore library capabilities and document the results?

Yes, you can use TDD and library exploration as flexible validation methods to test technical constraints, with all findings, constraints, and next steps captured in dual-language validation docs.

Does this validation workflow support generating documentation for both agents and users?

Yes, the validation workflow supports generating documentation for both agents and users by producing dual-language validation reports in English and Korean to ensure transparent decision making.

What format should the analysis and validation documents follow for this workflow?

The workflow requires loading analysis from docs/work/WORK-<task-name>/analysis.md and outputs dual-language validation documents to docs/work/WORK-<task-name>/validation.*.