documentation-planlisted

Use when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).
dtsong/my-claude-setup · ★ 5 · Data & Documents · score 76

Install: claude install-skill dtsong/my-claude-setup

# Documentation Plan ## Purpose Design a comprehensive documentation architecture that maps content types to audiences, defines onboarding paths, and establishes maintenance schedules. Produces a documentation strategy that scales with the team and codebase. ## Scope Constraints Reads existing documentation, project structure, and team context to produce a documentation strategy. Does not create or modify actual documentation files or deploy documentation infrastructure. ## Inputs - Project type and scope (library, application, platform, API) - Target audiences (developers, API consumers, end users, operators) - Current documentation state (what exists, what's missing, what's stale) - Team size and growth expectations ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Identify documentation audiences - [ ] Step 2: Map documentation types needed - [ ] Step 3: Define documentation structure - [ ] Step 4: Specify format and location - [ ] Step 5: Plan developer onboarding flow - [ ] Step 6: Design documentation testing - [ ] Step 7: Define maintenance schedule ### Step 1: Identify Documentation Audiences Map each audience and their needs: - **New developers**: Getting started, local setup, architecture overview, "where is X?" answers - **Experienced team members**: API reference, design decisions, runbooks, troubleshooting guides - **