documentation-currency

Detects stale documentation - outdated status markers, old TODOs, version lag

allowed_tools: Read, Grep, Glob

$ 安裝

git clone https://github.com/akaszubski/autonomous-dev /tmp/autonomous-dev && cp -r /tmp/autonomous-dev/plugins/autonomous-dev/skills/documentation-currency ~/.claude/skills/autonomous-dev

// tip: Run this command in your terminal to install the skill


name: documentation-currency version: 1.0.0 type: knowledge description: Detects stale documentation - outdated status markers, old TODOs, version lag category: validation auto_activate: false allowed-tools: [Read, Grep, Glob] keywords:

  • documentation
  • currency
  • stale
  • outdated
  • version
  • lag

Documentation Currency Skill

Purpose: Detect documentation that has become stale or outdated over time.

When This Skill Activates

  • Keywords:

Core Concepts

Overview

This skill provides comprehensive guidance on documentation currency. For detailed patterns and implementation examples, see the documentation files in docs/.

Key Topics:

  • Detailed methodologies and best practices
  • Implementation patterns and examples
  • Common pitfalls and anti-patterns
  • Cross-references to related skills

See: Documentation files in docs/ directory for complete details


Quick Reference

TopicDetails
Detailed Guide 1docs/detailed-guide-1.md
Detailed Guide 2docs/detailed-guide-2.md

Progressive Disclosure

This skill uses progressive disclosure to prevent context bloat:

  • Index (this file): High-level concepts and quick reference (<500 lines)
  • Detailed docs: docs/*.md files with implementation details (loaded on-demand)

Available Documentation:

  • docs/detailed-guide-1.md - Detailed implementation guide
  • docs/detailed-guide-2.md - Detailed implementation guide

Cross-References

Related Skills:

  • See PROJECT.md for complete skill dependencies

Related Tools:

  • See documentation files for tool-specific guidance

Key Takeaways

  1. Research existing patterns before implementing
  2. Follow established best practices
  3. Refer to detailed documentation for implementation specifics
  4. Cross-reference related skills for comprehensive understanding