Verify that every Must Have requirement in SPEC.md is implemented in the codebase.
npx skills add https://github.com/Hoang604/get-thing-done --skill verify-spec
Please help me install this Agent Skill. Skill: verify-spec Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/verify-spec Command: npx skills add https://github.com/Hoang604/get-thing-done --skill verify-spec
Verifies that all "Must Have" requirements defined in SPEC.md are implemented in the codebase, ensuring software quality and alignment with specifications.
Provide the task name to verify and review the resulting PASS/FAIL report for SPEC.md coverage.
High-intent search queries and answers about installing and using this skill.
To verify must-have requirements in a SPEC.md, you can automate SPEC verification by extracting requirements from ./.gtd/<task_name>/SPEC.md and auditing code paths for evidence. This returns a concise PASS/FAIL report with per-requirement evidence and suggested next steps.
Auditing code for spec compliance involves validating the presence and correctness of every must-have item across files, tests, and configuration. This process checks traceability and returns a clear report with remediation guidance for any failed items.
To check if your codebase matches must-have items, provide the task name to locate the SPEC.md file. The verification process extracts requirements and audits the code across files to generate a clear PASS/FAIL report with evidence.
Yes, you can automate generating a remediation report for failed spec requirements. The verification process audits code paths and configuration for coverage, returning a PASS/FAIL report that includes specific remediation guidance for any items that fail.
To start verifying your SPEC.md must-haves, you need to provide the specific task name. This allows the verification process to locate the ./.gtd/<task_name>/SPEC.md file, extract the requirements, and audit the codebase for implementation evidence.
Spec verification returns a FAIL status when a must-have requirement lacks implementation evidence in the codebase. The resulting report highlights the missing coverage across files and tests, providing suggested next steps and remediation guidance.
Hoang604Interview users to generate a SPEC.md with goals, constraints, and acceptance criteria.
databricks-solutionsAnalyze spec coverage data and test annotations to identify coverage gaps.
KubrickCodeDocument issues and bug reports with structured templates.
imgamerOrchestrate a full QA cycle from strategy to sign-off for game development stories.
