Skip to main content

Epic 9: Release Candidate Readiness

Status: TODO
Priority: HIGH
Estimated Effort: [TBD]
Created: 2026-01-16
Last updated: 2026-01-17 (v0.9.1.8+9 – E9:S01:T08 COMPLETE: Final validation complete - Kanban board S00→S01 references fixed, versioning policy E6:S06→E6:S07 corrected, acceptance criteria marked complete)
Branch: epic/9-release-candidate-readiness
Version Schema: 0.9.S.T+B
Production URL: [N/A for this repo]

Story Checklist​

Overview​

This epic addresses the critical gap between current project state (RC=0, development phase, no M/S priority tasks) and true Release Candidate (RC=1) readiness. The work involves comprehensive framework reviews, installation scenario analysis, migration path documentation, and strategic prioritization to move the project from development to release candidate state.

Problem Statement:

  • Current state shows no M (Must Have) or S (Should Have) priority tasks, suggesting readiness
  • However, project is at RC=0 (development phase), indicating we're not actually ready
  • Need to understand the gap and create a clear path to RC=1

Solution:

  • Comprehensive gap analysis to understand current vs RC=1 state

  • Framework-by-framework RC readiness reviews covering:

    • Package management (how packages are managed)
    • Package maintenance (how packages are maintained)
    • Package installation (how packages are installed, including all scenarios)

  • Canonical E/S/T structure review and refinement

  • Strategic prioritization and roadmap creation

Goals​

  1. Understand the Gap: Identify exactly what's missing or mis-prioritized for RC=1 readiness
  2. Framework Readiness: Review each packaged framework for RC readiness covering:
    • Framework Review:
      • Main objective and purpose
      • Documentation completeness and quality
      • Component analysis (justification, definition, behavior validation)
    • Package Management: How the framework package is managed (versioning, dependencies, updates)
    • Package Maintenance: How the framework package is maintained (bug fixes, updates, support)
    • Package Installation:
      • Clean install into new project
      • Active project installation:
        • File location detection relative to target project structure
        • Data backup procedures
        • Data mapping from old structure to installed framework
    • Update Management: How to manage AI Dev Kit updates in target projects
  3. Canonical Structure Review: Review and refine core and extended canonical E/S/T sets
  4. Strategic Prioritization: Elevate critical work to M/S priority and create roadmap to RC=1
  5. Documentation Completeness: Ensure all framework review, package management, maintenance, and installation scenarios are documented
  6. Book Project Integration: Identify tie-in opportunities for the accompanying book project

Stories​

Story 1: RC Readiness Gap Analysis​

Brief Summary: Investigate and document the gap between current project state (RC=0, no M/S tasks) and true Release Candidate (RC=1) state, identifying mis-prioritized work, missing tasks, and creating a roadmap to release readiness.

Story Document: Story-001-rc-readiness-gap-analysis.md

Note: For detailed Story information (Status, Priority, Goals, Tasks, Acceptance Criteria, Dependencies, etc.), see the Story document linked above. This Epic document only provides a high-level reference.

Story 2: Kanban Framework RC Readiness Review​

Brief Summary: Comprehensive review of Kanban Framework for RC readiness, covering framework objective/documentation/component analysis, package management/maintenance/installation (clean install, active project with file location, backup, data mapping), update management, and book project tie-in opportunities.

Story Document: Story-002-kanban-framework-rc-readiness-review.md

Note: For detailed Story information, see the Story document linked above.

Story 3: Workflow Management Framework RC Readiness Review​

Brief Summary: Comprehensive review of Workflow Management Framework for RC readiness, covering framework objective/documentation/component analysis, package management/maintenance/installation (clean install, active project with file location, backup, data mapping), update management, and book project tie-in opportunities.

Story Document: Story-003-workflow-management-framework-rc-readiness-review.md

Note: For detailed Story information, see the Story document linked above.

Story 4: Numbering & Versioning Framework RC Readiness Review​

Brief Summary: Comprehensive review of Numbering & Versioning Framework for RC readiness, covering framework objective/documentation/component analysis, package management/maintenance/installation (clean install, active project with file location, backup, data mapping), update management, and book project tie-in opportunities.

Story Document: Story-004-numbering-versioning-framework-rc-readiness-review.md

Note: For detailed Story information, see the Story document linked above.

Story 5: Canonical E/S/T Review and Refinement​

Brief Summary: Review and refine the core and extended canonical Epic/Story/Task sets, ensuring they align with RC readiness requirements and project needs.

Story Document: Story-005-canonical-est-review-and-refinement.md

Note: For detailed Story information, see the Story document linked above.

Dependencies​

Blocks:

  • Strategic release planning decisions
  • Framework release readiness
  • RC=1 state transition
  • Task prioritization corrections

Blocked By:

  • None (can start immediately)

Coordinates With:

  • Epic 5 (Documentation Management): Documentation completeness for frameworks
  • Epic 6 (Framework Management): Framework health and versioning
  • Epic 7 (Codebase Maintenance): Code quality and review
  • Epic 8 (Tooling & Automation): Automation and tooling readiness
  • All Framework Epics (1-4): Framework-specific readiness reviews

Risks & Mitigations​

  • Scope Creep: Framework reviews could expand beyond RC readiness → Define clear RC readiness criteria upfront
  • Prioritization Conflicts: Elevating tasks to M/S may conflict with current priorities → Use evidence-based analysis
  • Missing Work Discovery: May discover significant missing work → Create phased approach, prioritize critical gaps
  • Timeline Uncertainty: RC readiness timeline may be longer than expected → Create realistic roadmap with milestones

References​

  • FR-032: FR-032-release-candidate-readiness-gap-analysis.md - Feature Request
  • Versioning Policy: docs/architecture/standards-and-adrs/dev-kit-versioning-policy.md - RC definition
  • Kanban Board: docs/project-management/kanban/kboard.md - Current task priorities
  • Epic 1: docs/project-management/kanban/epics/Epic-1/Epic-1.md - AI Dev Kit Core
  • Epic 2: docs/project-management/kanban/epics/Epic-2/Epic-2.md - Workflow Management Framework
  • Epic 3: docs/project-management/kanban/epics/Epic-3/Epic-3.md - Numbering & Versioning Framework
  • Epic 4: docs/project-management/kanban/epics/Epic-4/Epic-4.md - Kanban Framework

This Epic is part of the Kanban Framework. See packages/frameworks/kanban/ for complete framework documentation.