Epic 5: Documentation Management and Maintenance
Status: IN PROGRESS
Priority: HIGH
Estimated Effort: [TBD]
Created: 2025-12-05
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Branch: epic/5-documentation-management
Version Schema: 0.5.S.T+B
Production URL: [N/A for this repo]
Story Checklist
-
E5:S00 – Abstract Space (Epic-Level) - ABSTRACT SPACE (v0.5.0.0+0 – Epic-level abstract space only, no tasks)
- Story:
Story-000-fr-repo.md - Note: S00 is Epic-level abstract space only. Repository tasks migrated to S01 (E9:S01:T08).
- Story:
-
E5:S01 – FR Repo (PERPETUAL) - IN PROGRESS (PERPETUAL -
v0.5.1.75+1T75/FR-075; v0.5.1.32+0 T32; v0.5.1.74+3 T74; T73 FR-073)- Story:
Story-001-fr-repo.md - Note: S01 is the repository story (migrated from S00). S01 omitted from board displays (UX optimization).
- Story:
-
E5:S02 – Documentation Maintenance Framework - IN PROGRESS (T02-T04 complete, T06 intake ✅ v0.5.2.6+1; T01, T05 TODO — FR-063 impl pending)
- Story:
Story-002-documentation-maintenance-framework.md - Note: Renumbered from S01 to S02 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S03 – Documentation Quality Assurance - COMPLETE ✅ (v0.5.3.3+1, migrated from v0.5.2.3+1)
- Story:
Story-003-documentation-quality-assurance.md - Tasks: T01 ✅, T02 ✅, T03 ✅
- Note: Renumbered from S02 to S03 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S04 – Documentation Automation - IN PROGRESS (T01 complete, T02-T03 TODO)
- Story:
Story-004-documentation-automation.md - Note: Renumbered from S03 to S04 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S05 – Framework Documentation Management - IN PROGRESS
- Story:
Story-005-framework-documentation-management.md - Tasks: T01 TODO, T02 TODO, T03 TODO, T04 TODO, T05 ✅, T06 TODO, T07 ✅
- Note: Renumbered from S04 to S05 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S06 – Legacy Repository Incorporation - IN PROGRESS
- Story:
Story-006-legacy-repository-incorporation.md - Tasks: T01 ✅, T02-T25 TODO (25 tasks across 4 phases)
- Note: Renumbered from S05 to S06 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S07 – Policy Documentation Structure - IN PROGRESS (v0.5.7.1+1, migrated from v0.5.6.1+1 – Task 1 complete: Policy salience implementation)
- Story:
Story-007-policy-documentation-structure.md - Tasks: T01 ✅ COMPLETE (FR-022)
- Note: Renumbered from S06 to S07 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S08 – Knowledge Base - IN PROGRESS (v0.5.8.2+8 – T02 ✅ E4:S16:T05 gap log spec, validator)
- Story:
Story-008-knowledge-base.md - Note: Renumbered from S07 to S08 as part of repository story migration (E9:S01:T08)
- Story:
-
E5:S09 – Docusaurus Documentation Portal - IN PROGRESS (T01–T10 ✅ v0.5.9.10+2; portal story tasks complete)
- Story:
Story-009-docusaurus-documentation-portal.md - Note: Atomic FR chain for full Docusaurus adoption (
portal/→docs/publish, CI, deploy, search).
- Story:
Overview
Epic 5 owns the Documentation Management and Maintenance framework for the ai-dev-kit repository. This epic ensures that all documentation remains accurate, up-to-date, and consistent across the entire project.
Goals
-
Establish Documentation Maintenance Framework
- Define processes for keeping documentation current
- Create documentation review and update cadences
- Establish documentation quality standards
-
Implement Documentation Quality Assurance
- Create validation tools for documentation consistency
- Establish documentation review processes
- Implement automated documentation checks
-
Automate Documentation Maintenance
- Create tools for automated documentation updates
- Implement documentation synchronization workflows
- Build documentation health monitoring
Stories (Initial)
Story 1: FR Repo (PERPETUAL)
Status: IN PROGRESS (PERPETUAL)
Priority: HIGH
Estimated Effort: N/A (Perpetual repository)
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Repository story for all Feature Requests. Provides 1:1 traceability between FR numbers and task numbers.
Story: Story-001-fr-repo.md
Note: This story was migrated from S00 to S01 as part of repository story abstract space resolution (E9:S01:T08). S00 is now abstract space only.
Story 2: Documentation Maintenance Framework
Status: IN PROGRESS
Priority: HIGH
Estimated Effort: [TBD]
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Establish a framework for maintaining documentation accuracy and consistency across the dev-kit.
Tasks:
- E5:S02:T01 – Conduct comprehensive documentation hygiene analysis
- E5:S02:T02 – Define documentation maintenance policies
- E5:S02:T03 – Create documentation review cadences
- E5:S02:T04 – Establish documentation update triggers
Story: Story-002-documentation-maintenance-framework.md
Note: Renumbered from S01 to S02 as part of repository story migration (E9:S01:T08).
Story 3: Documentation Quality Assurance
Status: COMPLETE ✅
Priority: HIGH
Estimated Effort: [TBD]
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Implement quality assurance processes and tools for documentation validation.
Tasks:
- E5:S03:T01 – Create documentation consistency validators ✅
- E5:S03:T02 – Implement documentation review workflows ✅
- E5:S03:T03 – Build documentation health dashboards ✅
Story: Story-003-documentation-quality-assurance.md
Note: Renumbered from S02 to S03 as part of repository story migration (E9:S01:T08).
Story 4: Documentation Automation
Status: IN PROGRESS
Priority: MEDIUM
Estimated Effort: [TBD]
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Automate documentation maintenance tasks to reduce manual effort and improve consistency.
Tasks:
- E5:S04:T01 – Create automated documentation update scripts ✅
- E5:S04:T02 – Implement documentation synchronization workflows
- E5:S04:T03 – Build documentation change detection and notification
Story: Story-004-documentation-automation.md
Note: Renumbered from S03 to S04 as part of repository story migration (E9:S01:T08).
Story 8: Knowledge Base
Status: IN PROGRESS
Priority: HIGH
Estimated Effort: [TBD]
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Investigate the ramifications of the persistent knowledge base concept, including integration points, workflow impacts, tooling requirements, and agent capabilities; establish Notion hub and KB index for migration.
Tasks:
- E5:S08:T01 – Investigate persistent knowledge base concept and ramifications
- E5:S08:T02 – Notion hub, Knowledge Base container, and KB index ✅
Story: Story-008-knowledge-base.md
Story 9: Docusaurus Documentation Portal
Status: IN PROGRESS
Priority: HIGH
Estimated Effort: [TBD]
Last updated: 2026-04-19 (v0.5.9.11+2 – RW E5:S09:T11)
Goal:
Complete Docusaurus adoption: canonical docs/ ingest (with publish scope), green builds, IA, CI, hosting, search, and production URL go-live—tracked via FR-065–FR-071 plus E5:S09:T09 (Pages verification).
Tasks:
- E5:S09:T01 – Docusaurus site identity and config (FR-065) ✅ v0.5.9.1+2
- E5:S09:T02 – Canonical docs path and publish scope (FR-066) ✅ v0.5.9.2+2
- E5:S09:T03 – Production build corpus triage (FR-067) ✅ v0.5.9.3+1
- E5:S09:T04 – Navigation, sidebar IA, and landing (FR-068) ✅ COMPLETE (v0.5.9.4+1)
- E5:S09:T05 – CI build gate (FR-069) ✅ v0.5.9.5+1
- E5:S09:T06 – Deployment and hosting (FR-070) ✅ v0.5.9.6+1
- E5:S09:T07 – Site search (FR-071) ✅ v0.5.9.7+1
- E5:S09:T08 – Strict broken links (FR-067 FU-1) ✅ v0.5.9.8+2 — T08
- E5:S09:T09 – GitHub Pages go-live verification (FR-070 follow-up) ✅ v0.5.9.9+2 — T09
- E5:S09:T10 – Strict broken anchors (FR-067 FU-3) ✅ v0.5.9.10+2 — T10
Story: Story-009-docusaurus-documentation-portal.md
Dependencies
Blocks:
- Future documentation-dependent work
Blocked By:
- None
Coordinates With:
- Epic 6 (Framework Management) - Documentation about frameworks
- Epic 7 (Examples & Adoption) - User-facing documentation
References
docs/project-management/kanban/README.mddocs/project-management/rituals/policy/kanban-governance-policy.md