validate-idea

Validate idea documentation structure and phase-appropriate artifact readiness.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-idea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-idea
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/validate-idea
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-idea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate the completeness and readiness of idea documentation and its lifecycle artifacts to ensure a smooth progression to planning and execution.

Core Features & Use Cases

  • Completeness checks: README.md, project-brief.md, and alignment between briefs and descriptions.
  • Phase-aware validation: ensures required phase-specific files (critique.md, specs/, issues/) exist according to project phase.
  • Consistency checks: verifies alignment between README, project-brief, specs, issues, and ADRs; flags missing links or mismatches.

Quick Start

Use this skill to validate an idea by running: /validate-idea coordinatr or /validate-idea yourbench

Frequently Asked Questions about validate-idea

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

FAQPage Schema
How do I validate project documentation readiness for the planning phase?

To validate project documentation readiness, check that required artifacts like README.md and project-brief.md exist and maintain alignment. Phase-aware validation ensures the correct concept, planning, and development files are present before progressing to execution.

What documentation files are required to verify project alignment and specs?

Verifying project alignment requires README.md, project-brief.md, specs, issues, and ADRs. Consistency checks flag missing links or mismatches among these files to ensure structural completeness across the project lifecycle.

Do I need external dependencies to check project-brief and README consistency?

No external dependencies are needed to check project-brief and README consistency. The validation process enforces phase-appropriate artifacts and performs structural checks natively without requiring additional tools or packages.

When do I need to validate phase-specific files like critique.md and issues?

You need to validate phase-specific files like critique.md and issues when transitioning between concept, planning, and development phases. Phase-aware validation ensures the required artifacts for each specific lifecycle stage exist and are correctly aligned.

What is the best way to assess if ADRs and specs are aligned with a project brief?

The best way to assess ADR and spec alignment with a project brief is through consistency checks that verify links and dependencies. This validation flags mismatches between architectural decisions, specifications, and the core project description.

Why does my idea documentation fail validation for missing ADRs or specs?

Idea documentation fails validation for missing ADRs or specs because phase-aware checks enforce required artifacts. The validator flags missing links or structural mismatches to prevent incomplete documentation from progressing to execution.