Validate implementation plans against code, call chains, constraints, and test cases.
npx skills add https://github.com/fagemx/thyra --skill plan-validate-fagemx
Please help me install this Agent Skill. Skill: plan-validate Source: https://github.com/fagemx/thyra/tree/main/.claude/skills/plan-validate Command: npx skills add https://github.com/fagemx/thyra --skill plan-validate-fagemx
This Skill proactively identifies critical gaps and inconsistencies in implementation plans by cross-referencing them against actual codebase, call chains, architectural constraints, and test cases, preventing costly errors and rework.
Use the plan-validate skill to validate the plan located at 'path/to/plan.md'.
High-intent search queries and answers about installing and using this skill.
To find gaps in an implementation plan, validate it against the actual codebase, trace call chains, and check architectural constraints to identify inconsistencies before development begins. This cross-referencing prevents costly rework by catching missing steps early.
Validating a plan against call chains involves tracing data flow through functions to confirm all necessary modifications are accounted for. It cross-references plan steps with existing codebase patterns to ensure proposed changes accurately reflect the current code state.
To check if a feature plan violates architectural constraints, validate plan steps against the project rules defined in CONTRACT.md. This constraint adherence check ensures your proposed development aligns with established architectural guidelines before implementation.
Yes, you can review test cases for completeness and boundary conditions by validating proposed test modifications against edge cases. This test case review checks assertions to ensure all critical scenarios and boundary conditions are covered before coding begins.
The best way to prevent rework from incomplete plans is proactive gap analysis before development. Cross-referencing implementation details with codebase patterns, data flow, and constraints identifies critical missing steps early, saving development time and effort.
Yes, you need an existing codebase to perform plan validation. The process verifies implementation plans by cross-referencing them against actual code, tracing data flow, and checking architectural rules, requiring existing code to compare with the proposed plan.
MichaelSolatiGenerate a layer-organized control manifest from accepted ADRs and technical preferences.
sitharaj88Generate test suites matching project frameworks and conventions.
lis186Trace business logic execution paths from a given entry point.
Obsidian-OwlDetect unused exports, orphaned files, layer violations, and circular dependencies in changed code.
