Docs Workflow
When & Why to Use This Skill
The docs-workflow skill is a comprehensive documentation management tool designed to automate the creation, maintenance, and auditing of project documentation. It specializes in generating and synchronizing CLAUDE.md, README.md, and structured documentation directories, ensuring that project context remains accurate and up-to-date for both human developers and AI agents.
Use Cases
- Automated Project Initialization: Rapidly scaffold essential documentation files (CLAUDE.md, README.md) and directory structures for new Next.js, Cloudflare, or generic projects using smart, tech-stack-aware templates.
- Documentation Health Audits: Perform full-scale audits using /docs-update to identify broken internal links, stale content (not updated in 30+ days), and version mismatches between docs and package.json.
- AI Context Synchronization: Maintain a 'source of truth' for AI agents by using /docs-claude to automatically update tech stack details, file paths, and development rules within CLAUDE.md based on the current project state.
- Standardized Documentation Scaffolding: Generate professional-grade documentation structures including dedicated files for API references, system architecture, and database schemas to ensure project scalability.
| name | docs-workflow |
|---|---|
| description | | |
| Four slash commands for documentation lifecycle | /docs, /docs-init, /docs-update, /docs-claude. Create, maintain, and audit CLAUDE.md, README.md, and docs/ structure with smart templates. |
| Use when | starting new projects, maintaining documentation, auditing docs for staleness, or ensuring CLAUDE.md matches project state. |
| user-invocable | true |
docs-workflow
Last Updated: 2026-01-11 Purpose: Manage project documentation throughout its lifecycle
Overview
This skill helps you:
- Initialize documentation for new projects (CLAUDE.md, README.md, docs/)
- Maintain CLAUDE.md to match actual project state
- Audit all docs for staleness, broken links, outdated versions
Commands
| Command | Purpose |
|---|---|
/docs |
Main entry - shows available subcommands |
/docs-init |
Create CLAUDE.md + README.md + docs/ structure |
/docs-update |
Audit and maintain all documentation |
/docs-claude |
Smart CLAUDE.md maintenance only |
Quick Start
New Project
# In a new project directory
/docs-init
This will:
- Detect project type (Cloudflare Workers, Next.js, generic)
- Create CLAUDE.md from appropriate template
- Create README.md if missing
- Optionally scaffold docs/ directory
Existing Project
# Audit all documentation
/docs-update
# Or just maintain CLAUDE.md
/docs-claude
What Gets Created
CLAUDE.md
Project-specific context for Claude Code, including:
- Project overview and tech stack
- Development setup commands
- Architecture overview
- Key file locations
- Common tasks and workflows
Templates available:
CLAUDE-cloudflare.md- Cloudflare Workers + Vite + D1 projectsCLAUDE-nextjs.md- Next.js App Router projectsCLAUDE-generic.md- Any other project type
README.md
Standard README with:
- Project name and description
- Installation/setup instructions
- Usage examples
- Configuration
- Contributing guidelines
docs/ Directory (Optional)
Scaffolded documentation structure:
docs/ARCHITECTURE.md- System architecturedocs/API.md- API documentationdocs/DATABASE.md- Database schema
Smart Maintenance
/docs-claude Features
The CLAUDE.md maintenance command checks:
Tech Stack Match
- Does CLAUDE.md list technologies that match package.json?
- Are versions mentioned still accurate?
Referenced Files
- Do paths mentioned in CLAUDE.md still exist?
- Are there new important files not mentioned?
Section Freshness
- Is "Last Updated" date recent?
- Are there outdated patterns or commands?
Critical Rules
- For detected tech stack, are important rules present?
- E.g., Cloudflare project should mention wrangler.jsonc patterns
/docs-update Features
Full documentation audit including:
Date Freshness
- Compare doc dates against git history
- Flag docs not updated in >30 days
Version References
- Check npm package versions mentioned
- Suggest updates for outdated versions
Broken Links
- Verify internal markdown links
- Check that referenced files exist
Redundancy
- Identify duplicate content across files
- Suggest consolidation
Orphaned Files
- Find docs not referenced anywhere
- Suggest archiving or deletion
Project Type Detection
The skill auto-detects project type by looking for:
| Indicator | Project Type |
|---|---|
wrangler.jsonc or wrangler.toml |
Cloudflare Workers |
next.config.js or next.config.ts |
Next.js |
| Neither | Generic |
Additional indicators influence template content:
package.jsondependencies (React, Vite, etc.)- Database config files (drizzle.config.ts, prisma/schema.prisma)
- Auth config (clerk, better-auth)
Integration with Other Skills
- project-workflow: Use
/docs-initafter/plan-projectto add documentation - project-planning: Generated
IMPLEMENTATION_PHASES.mdreferenced in CLAUDE.md - cloudflare-worker-base: Cloudflare template includes Workers-specific patterns
Best Practices
When to Run Each Command
| Situation | Command |
|---|---|
| New project | /docs-init |
| After major changes | /docs-claude |
| Before release | /docs-update |
| Monthly maintenance | /docs-update |
CLAUDE.md Guidelines
- Keep it current - Update "Last Updated" when making changes
- Focus on project-specific - Don't duplicate generic tech docs
- Include common tasks - Commands you run frequently
- Reference, don't duplicate - Link to docs/ for detailed content
Templates
Templates are located in templates/ within this skill:
templates/
├── CLAUDE-cloudflare.md # Cloudflare Workers projects
├── CLAUDE-nextjs.md # Next.js projects
├── CLAUDE-generic.md # Generic projects
└── README-template.md # Standard README
Templates use placeholders:
{{PROJECT_NAME}}- Detected from package.json or folder name{{DATE}}- Current date{{TECH_STACK}}- Detected technologies