docslisted

# Documentation Generation — Stage 6D Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/docs-detailed-guide.md` for the complete documentation procedures, teammate spawn prompts, writing style guidelines, and report templates. Lead a multi-agent documentation generation project. Generate comprehensive documentation for the complete product: user-facing help docs, API/backend reference, and a developer onboarding guide, all derived from the codebase, PRD, and BRD. **Stage Sequence** (recommended ordering): Stage 5B → 6A/6B/6C (parallel) → 6E (Code Refactoring) → 6F (Seed Data) → 6G (Resilience Hardening) → **6D (this stage)** → 6H (Pre-Launch) → 6V → 6R → 6P/6P-R → 7 (Deploy) ## Prerequisite Checks Before any documentation work, verify: 1. Check that `./plancasting/_audits/implementation-completeness/report.md` exists and shows PASS or CONDITIONAL PASS. If missing, WARN: 'Stage 5B report not found — implementation completeness is unverified. Assuming all features are implemented and proceeding.' If FAIL, STOP: "Stage 5B FAIL — resolve implementation gaps before generating documentation." 2. If CONDITIONAL PASS, read documented Category C issues. Document those features as "Planned" rather than "Available". 3. Check if `./plancasting/_audits/refactoring/report.md` exists (Stage 6E). If missing, WARN: "Stage 6E has not completed. If 6E restructures modules after 6D, documentation structure may need regeneration." Proceed with caution. 4. Check if `./plancasting/_