Analyze spec.md, plan.md, and tasks.md for gaps and inconsistencies.
npx skills add https://github.com/juvenal/openrender --skill speckit-analyze-juvenal
Please help me install this Agent Skill. Skill: speckit-analyze Source: https://github.com/juvenal/openrender/tree/main/.qwen/skills/speckit-analyze Command: npx skills add https://github.com/juvenal/openrender --skill speckit-analyze-juvenal
This Skill eliminates the risk of costly rework and failed implementations caused by undetected gaps, duplications, and inconsistencies between a project's core spec-kit artifacts (spec.md, plan.md, tasks.md), which are often only discovered late in the development cycle.
Use the speckit-analyze skill to review your spec.md, plan.md, and tasks.md files for gaps and inconsistencies after generating your task list.
High-intent search queries and answers about installing and using this skill.
To check for spec and plan inconsistencies before implementation, run a cross-artifact consistency analysis across spec.md, plan.md, and tasks.md to identify gaps, duplications, and misalignments. This read-only validation flags critical coverage issues without modifying project files.
You need to validate requirement coverage in spec-kit projects immediately after generating your tasks.md file. Running a pre-implementation check at this stage catches missing task coverage for key requirements and flags conflicting technical choices before you write any code.
No, speckit-analyze does not modify project files during consistency analysis. It performs a strictly read-only validation of your spec.md, plan.md, and tasks.md to flag critical misalignments, coverage gaps, and ambiguous requirements safely.
To validate constitution alignment against your project tasks, run a constitution-aware consistency analysis across your spec-kit artifacts. This process automatically flags any conflicts with the project's non-negotiable constitution rules as critical issues during the review.
No, you cannot use this cross-artifact analysis for projects without a .specify directory. The consistency analysis specifically applies to spec-kit projects that contain the .specify/ directory structure to validate alignment between requirements, architecture plans, and tasks.
The best way to catch duplicate requirements across spec, plan, and task files is to perform an automated cross-artifact consistency scan. This identifies duplicate requirements and ambiguous language across spec.md, plan.md, and tasks.md to eliminate the risk of costly rework.
jineyneAnalyze spec.md, plan.md, and tasks.md for cross-artifact inconsistencies and coverage gaps.
XinheLIUCompare spec.md, plan.md, and tasks.md to produce a read-only Markdown audit report.
gherrerzAssess a codebase against feature specs and append missing tasks to tasks.md.
refactory-langAnalyze spec.md, plan.md, and tasks.md for gaps, duplications, and inconsistencies.
