~aod-project-plan

Validate plan.md files against required architecture sections and artifacts.

86|21|Updated Mar 21, 2026

Search Tags:#architecture #validation #review #plan.md #architecture-docs #design-artifacts #spec-alignment

Ready to run

npx skills add https://github.com/davidmatousek/tachi --skill aod-project-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ~aod-project-plan
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/~aod-project-plan
Command: npx skills add https://github.com/davidmatousek/tachi --skill aod-project-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture documentation completeness validation across plan.md files, ensuring essential sections and design artifacts are present and aligned with the feature specification.

Core Features & Use Cases

Validates presence of Technical Context, Constitution Check, Project Structure, Technology Stack in plan.md
Checks for design artifacts (data-model.md, contracts/, research.md) and alignment with specs
Generates a validation report indicating READY or NOT READY and lists issues

Quick Start

Provide an architecture validation by running the validator against specs/*/plan.md to confirm completeness and alignment with the feature specification.

Frequently Asked Questions about ~aod-project-plan

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

FAQPage Schema

How do I validate architecture documentation completeness for a feature spec?▼

You validate architecture documentation by running a validator against specs/*/plan.md files to confirm the presence of Technical Context, Constitution Check, Project Structure, and Technology Stack sections, ensuring alignment with the feature specification.

What sections are required in a plan.md for pre-implementation review?▼

A plan.md pre-implementation review requires Technical Context, Constitution Check, Project Structure, and Technology Stack sections to be present and correctly aligned with the feature specification before development begins.

How do I check if data-model.md and contracts align with my specs?▼

You check alignment by validating your architecture docs for required design artifacts like data-model.md, contracts, and research.md, verifying they match the corresponding feature specification in your specs directory.

Does architecture validation generate a report indicating if a plan is ready?▼

Architecture validation generates a report indicating READY or NOT READY status and lists specific issues found in the plan.md file, helping you track missing sections or misaligned design artifacts before implementation.

When do I need to validate architecture docs before starting implementation?▼

You need architecture validation during pre-implementation reviews to ensure your plan.md across specs is complete, preventing downstream development issues caused by missing design artifacts or misaligned feature specifications.

What happens if my plan.md is missing the Technical Context section?▼

If plan.md is missing Technical Context, the architecture validation marks the file as NOT READY and lists the missing section as an issue in the generated report, blocking the pre-implementation review process.