spec-validate

Drive structured question-based validation workflows for Initiatives, Features, and Tasks.

1|Updated Jan 12, 2026

Search Tags:#specification #clarification #gates #validate #workflows #spec-create

Ready to run

npx skills add https://github.com/srnnkls/tropos --skill spec-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-validate
Source: https://github.com/srnnkls/tropos/tree/main/skills/spec-validate
Command: npx skills add https://github.com/srnnkls/tropos --skill spec-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validation loop for speccing. Clarifies requirements through structured questioning before document creation.

Core Features & Use Cases

Reference: See reference/issue-types.md for taxonomy and scope
Issue type selection: Distinguishes Initiative, Feature, Task, or Exploratory
Taxonomy-driven ambiguity scan: Identifies gaps early
Validation loop: Iterative clarification batches until coverage
SDD and gates: Supports pre-implementation gates for Initiatives and opt-ins for Features
Output: Produces validation data for spec-create (validation.yaml, plus logs)

Quick Start

Run the spec-validate skill to generate validation data by guiding you through issue type selection and clarification questions.

Frequently Asked Questions about spec-validate

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

FAQPage Schema

How do I validate and clarify requirements before writing a specification document?▼

To validate requirements, you can use a structured, question-based specification workflow that performs taxonomy-driven ambiguity scanning and iterative clarification. This identifies gaps early, resolving issues before documentation begins.

What is the best way to scan requirements for ambiguity before implementation?▼

Scanning for ambiguity is best handled by a taxonomy-driven validation loop that batches iterative clarification questions. This ensures full coverage and enforces pre-implementation gates for Initiatives.

How do I enforce specification gates and traceable clarification logs for features?▼

You can enforce specification gates and traceable clarification logs by driving a structured validation workflow. It produces a validation.yaml and related artifacts that enforce SDD opt-ins and front-to-back governance.

Does this specification validation workflow support different issue types like initiatives and tasks?▼

Yes, the specification validation workflow supports Initiatives, Features, and Tasks by performing issue-type selection. It distinguishes between these categories to apply the correct scope and governance rules.

What format does the validation output need to be in for spec creation?▼

The validation output needs to be in a validation.yaml format, accompanied by traceable clarification logs. These artifacts are specifically generated to ensure readiness for the spec-create process.