architecture-validator

Validate plan.md completeness and alignment with feature specifications.

1|Updated Mar 8, 2026

Search Tags:#architecture #documentation #specification #validation #plan.md #design-review

Ready to run

npx skills add https://github.com/tense-i/stock-market-simulator --skill architecture-validator-tense-i

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-validator
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/architecture-validator
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill architecture-validator-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates architecture documentation completeness by ensuring plan.md contains required sections, relevant design artifacts exist, and alignment with feature specifications, preventing incomplete designs from advancing.

Core Features & Use Cases

Checks for mandatory sections in plan.md (Technical Context, Constitution Check, Project Structure, Technology Stack)
Verifies presence of design artifacts (data-model.md, contracts, research)
Produces a readiness report to guide architectural reviews and approvals

Quick Start

Run architecture validation on specs/*/plan.md to verify completeness and alignment with the feature specification.

Frequently Asked Questions about architecture-validator

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

FAQPage Schema

How do I check if my architecture documentation is complete before implementation?▼

Architecture validation checks if plan.md contains required sections like Technical Context, Constitution Check, Project Structure, and Technology Stack. It verifies design artifacts exist and produces a readiness report to prevent incomplete designs from advancing into implementation.

What sections should a plan.md file include to pass architecture validation?▼

Architecture validation requires plan.md to include Technical Context, Constitution Check, Project Structure, and Technology Stack sections. It also checks for relevant design artifacts like data-model.md, contracts, and research documents to ensure full alignment with the feature specification.

How do I validate that design artifacts like data models and contracts align with feature specs?▼

Architecture validation verifies the presence of design artifacts such as data-model.md, contracts, and research files alongside plan.md. It cross-references these artifacts with the feature specification to ensure technical context and project structure are fully aligned before implementation begins.

Does architecture validation work for feature teams needing evidence of design readiness?▼

Architecture validation is designed for feature teams and technical validators needing evidence that required sections and artifacts exist. It outputs a structured validity report that guides architectural reviews and approvals by confirming documentation completeness.

What is the best way to automate architectural readiness checks for feature specifications?▼

Architecture validation automates readiness checks by scanning specs/*/plan.md files for mandatory sections and design artifacts. It generates a structured report confirming alignment with the feature specification, streamlining the design review and approval process without manual inspection.

Why does my architecture design review fail when required documentation is incomplete?▼

Architecture validation fails reviews when plan.md lacks mandatory sections like Technical Context or Constitution Check, or when artifacts like data-model.md and contracts are missing. It outputs a structured report highlighting these gaps to prevent incomplete designs from advancing.