Validate Docs Implementation
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill validate-docs-implementationgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/validate-docs-implementation ~/.claude/skills/validate-docs-implementationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Validate Documentation vs Implementation **Purpose**: Systematically identify and fix mismatches between actual implementation code and documentation. **Load When**: - User says: "validate docs", "check documentation", "docs vs implementation" - User mentions: "documentation mismatch", "docs don't match code" - After major code changes that may affect docs - During pre-release validation **Core Value**: Ensures documentation accurately reflects actual implementation, preventing user confusion and wasted debugging time. --- ## Quick Reference **What This Skill Does**: 1. ✅ Analyzes implementation code (scripts, core logic) 2. ✅ Identifies what the code actually creates/does 3. ✅ Searches all documentation for references to those entities 4. ✅ Compares documented behavior vs actual behavior 5. ✅ Fixes all mismatches systematically 6. ✅ Provides summary of changes made **Typical Mismatches Found**: - File names (e.g., docs say "design.md" but code creates "plan.md") - Folder structure (e.g., docs missing "02-resources/" directory) - Counts (e.g., docs say "3 files" but script creates "4 directories + 3 files") - Naming conventions (e.g., old vs new terminology) - References to deprecated features --- ## Workflow: 5-Step Validation Process ### Step 1: Analyze Implementation **Goal**: Understand what the code actually does **Actions**: 1. Read the implementation file(s) identified by user 2. Document exactly what it creates/generates/does:
Details
- Skill name
validate-docs-implementation- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/validate-docs-implementation/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Validate Docs Implementation skill do?
Load when user says "validate docs", "check documentation consistency", "docs vs implementation", or "find documentation mismatches". Systematically compares implementation code against documentation to identify and fix inconsistencies.
How do I install the Validate Docs Implementation skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Validate Docs Implementation popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Value Stream Mapping
5vnovakovits/claude-skills
Map how a request flows from ask to value — Mike Rother & John Shook's "Learning to See" (1999) and Karen Martin & Mike Osterling's "Value Stream Mapping" (2013), adapted to software and knowledge work. Covers scoping one value stream, the map grammar (process boxes with lead time, process time and %C&A, queue triangles, push and pull arrows, information flow, the timeline ladder, kaizen bursts), collecting real numbers from tracker state history instead of opinions, the summary metrics (total lead time, process time, flow efficiency or activity ratio, rolled %C&A), the future-state questions,
User Story Mapping
5vnovakovits/claude-skills
Apply Jeff Patton's User Story Mapping (O'Reilly, 2014) — arranging user stories into a two-dimensional map that preserves the user's narrative journey, which a flat backlog destroys. Covers the map's anatomy (backbone and ribs; activities, tasks, details), the two axes (narrative flow left-to-right, priority/necessity top-to-bottom), the core philosophy (shared understanding over documents; minimize output, maximize outcome and impact), running a mapping workshop (frame, map breadth-first, explore alternatives/exceptions, distill a backbone, slice), slicing releases into a walking-skeleton MV
Writing Plans
8Freddy-CHEN-ux/00_claude_skills
Use after brainstorming, before implementation. Breaks work into discrete, actionable tasks with clear verification points.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.