nfr-outdated-check

To check AWS non-functional requirement sheets for outdated statements, you can scan your survey markdown files against current AWS service specifications and official guidance. This generates a structured report with file references and recommended fixes to restore accuracy.

Auditing non-functional requirements against current AWS best practices involves comparing your hearing sheet contents with the latest official AWS documentation. The process applies a defined taxonomy to classify findings and produces an audit-ready report highlighting outdated content and suggested edits.

You can generate an audit report for outdated AWS service guidance by scanning your NFR markdown files and classifying the findings using a dedicated taxonomy. The output is a structured report containing file references and recommended fixes, suitable for steering committee review.

Yes, the outdated content detection specifically targets survey/doc_source/nfr-*.md files. It uses the taxonomy defined in .claude/references/nfr-taxonomy.md to classify findings and generates a report named with the current date for steering or review purposes.

When scanning non-functional requirement sheets for AWS accuracy, the process is limited to identifying outdated statements by cross-referencing AWS service specifications with official guidance. It requires properly formatted survey markdown files and a specific taxonomy file to classify and recommend fixes correctly.