validating-roadmap

Phase-based contradiction detection systematically compares roadmap timelines, API contracts, data models, and specification requirements to surface conflicts. The Skill analyzes multi-document artifacts—specifications, SKILL.md, and ROADMAP files—then outputs contradictions with locations and severity, enabling targeted resolution before implementation.

Gap analysis scans specifications and roadmaps for missing requirements across storage strategies, API contracts, data models, and user experience considerations. It identifies unfulfilled dependencies, undefined milestones, and incomplete feature coverage, returning a structured list of implementation gaps organized by phase and priority.

Roadmap realism validation checks dependencies, milestone sequencing, and specification completeness against your roadmap timeline. It identifies circular dependencies, resource conflicts, and misaligned phases, producing recommendations to adjust scope, timing, or resource allocation for feasibility.

Yes. The Skill processes multi-document specifications, roadmaps, and design references simultaneously, detecting inconsistencies in naming conventions, API versioning, data model definitions, and requirements clarity. Output includes specification quality issues flagged by document and category.

Output comprises an executive summary, contradictions found with context, implementation gaps by phase, specification quality issues by document, roadmap recommendations, role responsibilities, and a defined review process—all formatted deterministically in Markdown for stakeholder review.

Run validation before committing roadmap phases, when specifications change materially, after cross-team planning sessions, or before milestone reviews. Early validation prevents costly misalignment; regular checks maintain coherence as requirements evolve across storage, APIs, data models, and UX.