What problem does it solve? Manual verification of document metadata—such as checking that a REQ or Decision file's frontmatter ID matches its filename, confirming an ID appears in a README index, or ensuring edits stay within an allowed path scope—is error-prone when done by LLM reasoning alone. This Skill replaces that judgment with deterministic, testable scripts that return structured JSON results. ## Core Features & Use Cases - Frontmatter Consistency Check: Verifies that frontmatter id values match filenames for REQ-NNNN, ADR-NNNN, and DEC-NNN Markdown files in a directory. - Entry Existence Check: Confirms a given ID (e.g., REQ-0001) appears in one or more README index files. - Change Impact Validation: Compares a list of changed file paths against an allowed path prefix list and reports violations outside the permitted scope. - Use Case: During a case-ready workflow, run the change-impact script against the set of edited files and the allowed path list to mechanically prove no out-of-scope files were modified before saving a Definition package. ## Quick Start Ask the agent to run the artifact-validation scripts to verify that all requirement files in docs/requirements have frontmatter IDs matching their filenames and report the JSON result.
