documentation-writing

Audit and edit project documentation in the .claude/skills/project-knowledge/references/ directory.

244|75|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill documentation-writing-pavel-molyanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-writing
Source: https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/documentation-writing
Command: npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill documentation-writing-pavel-molyanov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain and audit project documentation, ensuring it remains accurate, concise, and useful for understanding the project without needing to read the code.

Core Features & Use Cases

  • Audit Documentation: Checks for code blocks, duplication, and outdated information, providing a report of issues.
  • Edit & Update: Modifies specific files or sections of documentation based on user requests.
  • Check Consistency: Verifies terminology and data points across all documentation files.
  • Show Status: Reports on the completeness and state of documentation files.
  • Use Case: After a new feature is implemented, use this Skill to update the architecture.md and project.md files to reflect the changes, ensuring new team members can quickly grasp the project's current state.

Quick Start

Use the documentation writing skill to audit all files in .claude/skills/project-knowledge/references/.

Frequently Asked Questions about documentation-writing

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

FAQPage Schema
How do I audit project documentation for outdated information and duplication?

Auditing project documentation involves scanning files like project.md and architecture.md to detect code blocks, duplication, and outdated data. This skill generates a status report highlighting inconsistencies and issues across your references directory.

What is the best way to keep technical documentation consistent after implementing new features?

Keeping technical documentation consistent requires verifying terminology and data points across all files. This skill checks consistency in your project knowledge directory and edits specific sections to reflect code changes accurately.

How do I update architecture.md and project.md files without reading the entire codebase?

Updating architecture.md and project.md files is handled by editing specific sections based on user requests. The skill modifies documentation directly, ensuring new team members understand the project state without reading code.

Can I check the completeness and status of core documentation files like deployment.md and patterns.md?

Checking the completeness of deployment.md and patterns.md is supported through a status reporting feature. The skill evaluates the state of these core files within the references directory and reports their current completeness.

Why should project documentation avoid code blocks, and how can I check for them?

Avoiding code blocks in project documentation ensures it remains concise and useful for high-level understanding without duplicating the codebase. This skill audits your files and flags any code blocks that violate this documentation principle.