doc-update

Clean Markdown project documentation by removing outdated details and code snippets.

2|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/kojder/photo-map-app --skill doc-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-update
Source: https://github.com/kojder/photo-map-app/tree/main/.claude/skills/doc-update
Command: npx skills add https://github.com/kojder/photo-map-app --skill doc-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines project documentation by cleaning up Markdown files, removing verbose implementation details, and pruning outdated sections while preserving essential architectural decisions and technical context.

Core Features & Use Cases

  • Documentation cleanup: condense feature docs, READMEs, investigations, and CLAUDE references to only the essential information.
  • Organization & consistency: standardize headings, structure, and terminology across the repository.
  • Use Case: when a user asks to "update X docs" or "organize documentation", run this Skill to produce a lean, maintainable docs set.

Quick Start

Use the doc-update skill to clean up README.md and reorganize .ai/features/ markdown for the Photo Map MVP.

Frequently Asked Questions about doc-update

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

FAQPage Schema
How do I clean up and organize project documentation in Markdown?

Documentation cleanup removes verbose implementation details and outdated sections from Markdown files while preserving essential architectural decisions and technical context. This produces lean, maintainable docs that improve decision-making velocity across the team.

What should I keep when removing noise from README and feature documentation?

Preserve architectural decisions, technical context, and high-value information for future development. Remove code snippets, verbose implementation details, and outdated sections that clutter understanding without adding substance.

Can I standardize documentation structure across multiple Markdown files at once?

Yes. The Skill organizes and standardizes headings, structure, and terminology across repository documentation including README.md, PROGRESS_TRACKER.md, CLAUDE.md, and .ai/features/ directories in a single pass.

When should I update project documentation beyond just fixing errors?

Update documentation when feature sets evolve, architectural decisions change, or docs accumulate verbose details that slow onboarding and decision-making. Regular cleanup keeps documentation aligned with current project state.

How does lean documentation improve project maintainability?

Lean documentation reduces cognitive load by focusing on essential context rather than implementation minutiae. Teams make faster decisions with less search friction, and new contributors onboard more efficiently with clear, concise architectural guidance.

What file types and locations does documentation cleanup cover?

Cleanup covers all Markdown files in scope, including core docs like README.md and PROGRESS_TRACKER.md, feature documentation in .ai/features/, CLAUDE.md references, and any other Markdown files you reference.