Verified:GitHub

wa:validate-docs

Validates feature documentation via AC-ID traceability, freshness, terminology, and artifact consistency checks.

Updated Mar 26, 2026

Search Tags:#technical writing #documentation quality #artifact consistency #AC-ID traceability #doc freshness #terminology compliance #e2e lifecycle

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:validate-docs
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/validate-docs
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incomplete or stale feature documentation from passing lifecycle checkpoints by validating AC-ID traceability, doc freshness, terminology compliance, and cross-artifact consistency.

Core Features & Use Cases

AC-ID traceability scoring: Verifies that active AC-IDs are specified, planned, and implemented using the coverage-report primitive.
Doc freshness checks: Detects documentation that no longer matches changed code and flags stale references.
Terminology compliance: Scans feature docs for deprecated terms and reports non-compliant usage with canonical replacements.
Artifact consistency validation: Confirms FRD/TASKS/DESIGN-REVIEW cross-references and status alignment for completeness.

Use case: During an E2E lifecycle run, validate that a newly changed feature’s docs accurately track what was implemented and that all acceptance criteria are traceable end-to-end.

Quick Start

Run the validate-docs skill against a feature description to get per-check PASS/WARN/FAIL results and an overall documentation quality score.

Frequently Asked Questions about wa:validate-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate AC-ID traceability in feature documentation?▼

AC-ID traceability validation verifies that active acceptance criteria are specified, planned, and implemented. It applies coverage-report scoring to produce per-check PASS/WARN/FAIL results and a composite documentation quality verdict.

What is the best way to check documentation freshness against changed code?▼

Doc freshness checks detect documentation that no longer matches changed code and flags stale references. This mechanism aligns changed-file updates with feature-scoped doc review to ensure technical writing accurately tracks implementations.

How does terminology compliance scanning work for feature docs?▼

Terminology compliance scanning scans feature docs for deprecated terms and reports non-compliant usage. It provides canonical replacements to enforce strict vocabulary standards during documentation quality lifecycle gatekeeping.

Can I validate FRD TASKS and DESIGN-REVIEW cross-references for consistency?▼

Artifact consistency validation confirms FRD, TASKS, and DESIGN-REVIEW cross-references and status alignment. It ensures end-to-end traceability and completeness for acceptance criteria during E2E lifecycle runs.

Do I need staged execution to gate documentation quality at lifecycle checkpoints?▼

Staged execution is required to gate documentation quality at lifecycle checkpoints. It mandates statusline updates, coverage scoring, and agent-dispatched technical writing checks to produce a composite verdict.