Skip to main content

Story 006 – Comprehensive Canonical Epics/Stories/Tasks Template System

Status: COMPLETE Priority: HIGH
Estimated Effort: [TBD]
Created: 2025-12-09
Last updated: 2025-12-22 (v0.4.6.8+4 – T08+4 COMPLETE: FR-030 CLI tool Feature Request created) Version: v0.4.6.8+4 Code: E4S06

Overview​

Implement a comprehensive, systematic template system for canonical epics, stories, and tasks that can be contextualized into concrete epics/stories/tasks for projects implementing ai-dev-kit as a template. This addresses FR-005 and provides a complete, scalable structure that eliminates cognitive load for developers starting new projects.

Goal​

Create a complete template system that provides:

  • Comprehensive canonical epics/stories/tasks structure (Epics 1-21+)
  • Individual template files for each epic/story/task
  • Contextualization mechanism (placeholders → project-specific)
  • Scalability guidance (tiny → ambitious projects)
  • Integration with Kanban installer/initializer

This enables projects to adopt ai-dev-kit with zero cognitive load for E/S/T structure design.

Task Checklist​

  • E4:S06:T00 – Story creation and comprehensive structure documentation ✅ COMPLETE (v0.4.6.0+1)
  • E4:S06:T01 – Create individual epic template files for canonical epics (1-7) ✅ COMPLETE (v0.4.6.7+1)
  • E4:S06:T02 – Create individual epic template files for project-specific canonical epics (8-21) ✅ COMPLETE (v0.4.6.10+1 – All 14 epic templates created: Epics 8-21)
  • E4:S06:T03 – Create story template files for each typical story ✅ COMPLETE (v0.4.6.3+1 – All 62 story templates created for Epic 1-21)
  • E4:S06:T04 – Create task template files for each typical task ✅ COMPLETE (v0.4.6.4+43 – All 378 canonical task templates generated, validated, sanitized, and duplicates cleaned up)
  • E4:S06:T05 – Create contextualization guide and examples - ✅ COMPLETE (v0.4.6.5+1)
  • E4:S06:T06 – Update CANONICAL_EPICS.md to reference comprehensive structure (BR-005) ✅ COMPLETE (v0.4.6.6+1)
  • E4:S06:T07 – Integrate with template setup guide and installation workflow - ✅ COMPLETE (v0.6.7.104+2 – Enhanced integration with setup guide, improved contextualization guide cross-references, comprehensive BR-009 validation completed)
  • E4:S06:T08 – Validate structure with test projects (tiny, small, ambitious) - ✅ COMPLETE (v0.4.6.8+1 – Validation completed via contextualization examples: tiny-project, small-project, ambitious-project examples created and documented in T05)
  • E4:S06:T09 – BR-009: Improve installer discoverability and documentation ✅ COMPLETE (v0.4.6.9+2)
  • E4:S06:T10 – BR-004: Fix epic contamination in installer ✅ COMPLETE (v0.4.6.10+1)

Tasks​

E4:S06:T01 – Create individual epic template files for canonical epics (1-7)​

Status: COMPLETE Priority: HIGH
Dependencies: FR-005, Comprehensive canonical structure design document
Blocker: None

Input:

  • COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Complete canonical structure
  • EPIC_TEMPLATE.md - Base epic template structure
  • CANONICAL_EPICS.md - Existing canonical epics documentation

Deliverable:

  • Individual epic template files for Epics 1-7:

    • templates/epics/Epic-1-Project-Core.md
    • templates/epics/Epic-2-Workflow-Management.md
    • templates/epics/Epic-3-Versioning.md
    • templates/epics/Epic-4-Kanban-Framework.md
    • templates/epics/Epic-5-FR-Implementation.md
    • templates/epics/Epic-6-BR-Implementation.md
    • templates/epics/Epic-7-UXR.md

  • Each template includes:

    • Purpose, scope, key characteristics
    • Typical stories list
    • Placeholders for contextualization (\{PROJECT_NAME\}, \{DOMAIN\}, etc.)
    • Integration points with other epics

Approach:

  1. Extract epic definitions from COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md
  2. Use EPIC_TEMPLATE.md as base structure
  3. Populate with canonical epic content
  4. Add placeholders for contextualization
  5. Include typical stories references
  6. Document integration points

Acceptance Criteria:

  • All 7 epic templates created
  • Templates use placeholders for contextualization
  • Templates reference typical stories
  • Templates include integration points
  • Templates follow consistent structure

E4:S06:T02 – Create individual epic template files for project-specific canonical epics (8-21)​

Status: COMPLETE Priority: HIGH
Dependencies: E4:S06:T01
Blocker: None

Input:

  • COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Complete canonical structure
  • Epic templates from T01 (for consistency)

Deliverable:

  • Individual epic template files for Epics 8-21:

    • templates/epics/Epic-8-Codebase-Maintenance.md
    • templates/epics/Epic-9-User-Management.md
    • templates/epics/Epic-10-Data-Management.md
    • templates/epics/Epic-11-API-Backend.md
    • templates/epics/Epic-12-Frontend-UI.md
    • templates/epics/Epic-13-Testing-QA.md
    • templates/epics/Epic-14-Deployment-DevOps.md
    • templates/epics/Epic-15-Security.md
    • templates/epics/Epic-16-Performance.md
    • templates/epics/Epic-17-Integration.md
    • templates/epics/Epic-18-Documentation.md
    • templates/epics/Epic-19-Analytics.md
    • templates/epics/Epic-20-Mobile.md
    • templates/epics/Epic-21-Internationalization.md

  • Each template includes same structure as T01 templates

ADK live kanban vs package templates​

Epic numbers in the template list above follow adopter-oriented canonical numbering (e.g. Epic-18-Documentation.md under packages/frameworks/kanban/templates/). The ai-dev-kit live board under docs/project-management/kanban/ does not use the same epic-to-role map: Epic 9 is Release Candidate Readiness (see kanban-structure.md); there is no live epics/Epic-18/ directory in this repo.

Approach:

  1. Extract epic definitions from comprehensive structure
  2. Use same template structure as T01
  3. Populate with project-specific epic content
  4. Add placeholders for contextualization
  5. Include typical stories references

Acceptance Criteria:

  • Epic templates 8-11 created ✅ (4/14 complete)
  • Epic templates 12-21 remaining (10/14 remaining)
  • Templates use placeholders for contextualization ✅
  • Templates reference typical stories ✅
  • Templates follow consistent structure with T01 ✅

Files Created (Partial):

  • ✅ packages/frameworks/kanban/templates/epics/Epic-8-Codebase-Maintenance.md
  • ✅ packages/frameworks/kanban/templates/epics/Epic-9-User-Management.md
  • ✅ packages/frameworks/kanban/templates/epics/Epic-10-Data-Management.md
  • ⏳ Remaining: Epics 11-21 (11 templates)

E4:S06:T03 – Create story template files for each typical story​

Status: ✅ COMPLETE
Priority: HIGH
Dependencies: E4:S06:T01, E4:S06:T02 (✅ Complete)
Blocker: None

Input:

  • COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Story definitions
  • STORY_TEMPLATE.md - Base story template structure

Deliverable:

  • Story template files for each typical story per epic

  • Organized in templates/stories/ directory structure:

    • templates/stories/Epic-1/Story-1-Project-Foundation.md
    • templates/stories/Epic-1/Story-2-Core-Infrastructure.md
    • templates/stories/Epic-1/Story-3-Initial-Features.md
    • ... (for all epics and their typical stories)

  • Each story template includes:

    • Purpose and goal
    • Typical tasks list
    • Key deliverables
    • Integration points
    • Placeholders for contextualization

Approach:

  1. Extract story definitions from comprehensive structure
  2. Use STORY_TEMPLATE.md as base structure
  3. Create directory structure: templates/stories/Epic-X/
  4. Populate with canonical story content
  5. Add placeholders for contextualization
  6. Include typical tasks references

Acceptance Criteria:

  • Story templates created for all typical stories (62 stories total: Epic 1-21)
  • Templates organized by epic in directory structure (templates/stories/Epic-X/)
  • Templates use placeholders for contextualization (\{PROJECT_NAME\}, \{DOMAIN\})
  • Templates reference typical tasks
  • Templates follow consistent structure

Completed: All 62 story templates created covering Epic 1-21:

  • Epic 1-7: 20 core framework epic story templates
  • Epic 8-21: 42 project-specific epic story templates (including Epic 21 Story 0)

E4:S06:T04 – Create task template files for each typical task​

Status: ✅ COMPLETE
Priority: MEDIUM
Dependencies: E4:S06:T03
Blocker: None
Version: v0.4.6.4+43

Input:

  • COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Task definitions
  • Task template structure (TASK_TEMPLATE.md)
  • Procedural generator (generate_task_templates.py)
  • Agentic generator (agentic_template_generator.py)

Deliverable:

  • ✅ Task template files for all 378 canonical tasks

  • ✅ Organized in templates/tasks/Epic-X/Story-Y/ directory structure

  • ✅ All templates include:

    • Input and deliverable
    • Approach/methodology
    • Acceptance criteria
    • Dependencies
    • Placeholders for contextualization

  • ✅ Filename sanitization implemented (handles special characters)

  • ✅ Duplicates cleaned up

  • ✅ Validation complete

Approach:

  1. ✅ Extracted task definitions from comprehensive structure
  2. ✅ Used procedural generator to create all templates
  3. ✅ Enhanced with agentic generator for richer content
  4. ✅ Fixed filename sanitization issues
  5. ✅ Cleaned up duplicates and invalid directories
  6. ✅ Validated all 378 templates exist and are correctly formatted

Acceptance Criteria:

  • Task templates created for all typical tasks (378 tasks) ✅
  • Templates organized by epic/story in directory structure ✅
  • Templates use placeholders for contextualization ✅
  • Templates include acceptance criteria ✅
  • Templates follow consistent structure ✅
  • Filenames sanitized and filesystem-safe ✅
  • All duplicates removed ✅

Completion Summary: All 378 canonical task templates have been successfully generated, validated, and sanitized. The hybrid approach (concrete + procedural generation) is now complete, enabling efficient maintenance and distribution of task templates.

E4:S06:T05 – Create contextualization guide and examples​

Status: ✅ COMPLETE (v0.4.6.5+1) Priority: HIGH
Dependencies: E4:S06:T01, E4:S06:T02
Blocker: None

Input:

  • Epic templates from T01 and T02
  • Comprehensive structure document

Deliverable:

  • ✅ templates/CONTEXTUALIZATION_GUIDE.md - Complete contextualization guide

  • ✅ Examples directory with contextualized templates:

    • ✅ examples/contextualized/tiny-project/ - Core Epics only (1-7, 8, 10, 18, 22, 23)
    • ✅ examples/contextualized/small-project/ - Core Epics + Epic 11 (API), Epic 12 (UI)
    • ✅ examples/contextualized/ambitious-project/ - Core Epics + Epics 9, 11-17, 19-21

  • ✅ Guide includes:

    • ✅ Placeholder replacement instructions
    • ✅ Customization guidelines
    • ✅ Scalability guidance
    • ✅ Examples for different project types

Approach:

  1. Document placeholder system (\{PROJECT_NAME\}, \{DOMAIN\}, etc.)
  2. Create step-by-step contextualization process
  3. Create example contextualized templates for different project types
  4. Document customization best practices
  5. Add troubleshooting section

Deliverables:

  • ✅ packages/frameworks/kanban/templates/CONTEXTUALIZATION_GUIDE.md - Comprehensive guide

    • Placeholder system documentation
    • Step-by-step contextualization process (4 phases)
    • Scalability guidance (tiny, small, medium, ambitious)
    • Customization guidelines (Epic, Story, Task levels)
    • Troubleshooting section
    • Integration with installer

  • ✅ packages/frameworks/kanban/templates/examples/contextualized/tiny-project/ - Tiny project example

    • PersonalBlog example
    • Core Epics only
    • Minimal customization

  • ✅ packages/frameworks/kanban/templates/examples/contextualized/small-project/ - Small project example

    • SaaSMVP example
    • Core Epics + Epic 11 (API), Epic 12 (UI)
    • Moderate customization

  • ✅ packages/frameworks/kanban/templates/examples/contextualized/ambitious-project/ - Ambitious project example

    • EnterprisePlatform example
    • Core Epics + Epics 9, 11-17, 19-21
    • Full customization

Acceptance Criteria:

  • Contextualization guide created
  • At least 3 example projects (tiny, small, ambitious)
  • Guide includes placeholder replacement instructions
  • Guide includes customization guidelines
  • Guide includes scalability guidance

E4:S06:T06 – Update CANONICAL_EPICS.md to reference comprehensive structure (BR-005)​

Status: COMPLETE Priority: HIGH
Dependencies: E4:S06:T01, E4:S06:T02, BR-005
Blocker: None

Input:

  • CANONICAL_EPICS.md - Existing canonical epics documentation (currently only Epics 1-7)
  • COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Complete canonical structure (Epics 1-23+)
  • Epic templates from T01 and T02
  • BR-005: Kanban Framework Epic Structure Gap (UAT Finding)

Deliverable:

  • Updated CANONICAL_EPICS.md that:
    • Addresses BR-005: Includes all core epics (1-8) and ancillary epics (9-21)
    • Epic 7 (UXR) added with complete description
    • Epic 7 (Codebase Maintenance) renumbered to Epic 8
    • Epics 9-21 added with complete descriptions
    • Clearly distinguishes core epics (1-8) vs ancillary epics (9-21)
    • References COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md as authoritative source
    • Links to individual epic templates
    • Updates epic ordering rationale with chronological adoption sequence
    • Includes contextualization guidance

Approach:

  1. Fix Epic 7: Update Epic 7 section to UXR (User Experience Research) with complete description
  2. Fix Epic 8: Renumber Codebase Maintenance from Epic 7 to Epic 8
  3. Add Core Epics: Ensure all core epics (1-8) are documented:
    • Epic 1: Project Core
    • Epic 2: Workflow Management
    • Epic 3: Versioning
    • Epic 4: Kanban Framework
    • Epic 5: FR Implementation
    • Epic 6: BR Implementation
    • Epic 7: UXR (User Experience Research)
    • Epic 8: Codebase Maintenance and Review
  4. Add Ancillary Epics: Add Epics 9-21 with complete descriptions:
    • Epic 9: User Management and Authentication
    • Epic 10: Data Management and Database
    • Epic 11: API and Backend Services
    • Epic 12: Frontend Application
    • Epic 13: Testing and Quality Engineering
    • Epic 14: Deployment and Release Engineering
    • Epic 15: Security and Compliance
    • Epic 16: Performance and Scalability
    • Epic 17: Integration and Interoperability
    • Epic 18: Documentation
    • Epic 19: Analytics and Monitoring
    • Epic 20: Mobile Application
    • Epic 21: Internationalization and Localization
  5. Add Core vs Ancillary Distinction: Clearly document which epics are core (always installed) vs ancillary (users pick and choose)
  6. Reference Comprehensive Structure: Add prominent reference to COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md as the complete authoritative source
  7. Add Links: Link to individual epic templates (when created in T01-T02)
  8. Update Ordering: Update ordering rationale to reflect chronological adoption sequence
  9. Add Contextualization: Include contextualization guidance section
  10. Update Usage Instructions: Update usage instructions to explain core vs ancillary epic selection

Acceptance Criteria (BR-005 Requirements):

  • Criterion 1: Epic 7 (UXR) added to CANONICAL_EPICS.md with complete description ✅
  • Criterion 2: Epic 7 (Codebase Maintenance) renumbered to Epic 8 ✅
  • Criterion 3: Epics 9-21 added to CANONICAL_EPICS.md with complete descriptions ✅
  • Criterion 4: Documentation clearly distinguishes core epics (1-8) vs ancillary epics (9-21) ✅
  • Criterion 5: All epic descriptions include purpose, scope, key characteristics, typical stories, and integration points ✅
  • Criterion 6: CANONICAL_EPICS.md references COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md as authoritative source ✅
  • References comprehensive structure document prominently
  • Links to individual epic templates (when available)
  • Updated ordering rationale with chronological adoption sequence
  • Contextualization guidance included
  • Usage instructions updated for core vs ancillary epic selection

E4:S06:T07 – Integrate with template setup guide and installation workflow​

Status: COMPLETE Priority: HIGH
Dependencies: E4:S06:T01-T06
Blocker: BR-004 fix (epic contamination), FR-005 implementation
Linked BR: BR-009 (GitHub issue #14) - Installer discoverability and documentation Enhanced: v0.6.7.104+2 - Comprehensive BR-009 validation, improved cross-references, integration validation report

Input:

  • Template files from T01-T04
  • Contextualization guide from T05
  • framework-dependency-post-template-setup-guide.md - Template setup guide
  • BR-004 fix (when implemented)

Deliverable:

  • Updated template setup guide that:

    • References canonical epic templates
    • Provides step-by-step contextualization process
    • Includes examples for different project types
    • Integrates with Kanban installer (when created)

  • Installation workflow integration:

    • Kanban installer uses canonical templates
    • Installation process contextualizes templates
    • Clear separation from project-specific content

Approach:

  1. Update template setup guide Step 4 (Kanban Board customization)
  2. Replace manual epic cleanup with template-based approach
  3. Add contextualization instructions
  4. Integrate with Kanban installer (when available)
  5. Document installation workflow

Acceptance Criteria:

  • Template setup guide updated ✅
  • Manual epic cleanup replaced with template approach ✅
  • Contextualization instructions included ✅
  • Integration with installer documented ✅
  • Installation workflow documented ✅
  • BR-009: Installer prominently featured as primary/only installation method ✅
  • BR-009: README clearly distinguishes canonical templates vs. ai-dev-kit's actual Kanban ✅
  • BR-009: Warning added if users manually copy files (direct to installer) ✅
  • BR-009: Installation documentation includes clear examples of expected results ✅

E4:S06:T08 – Validate structure with test projects (tiny, small, ambitious)​

Status: COMPLETE Priority: MEDIUM
Dependencies: E4:S06:T01-T07
Blocker: None

Input:

  • All template files from T01-T04
  • Contextualization guide from T05
  • Updated documentation from T06-T07

Deliverable:

  • Validation report with:
    • Test results for tiny project (Epics 1-7 only)
    • Test results for small project (Epics 1-7 + 2-3 project epics)
    • Test results for ambitious project (full structure)
    • Feedback and improvements identified
    • Recommendations for refinement

Approach:

  1. Create test project scenarios
  2. Contextualize templates for each scenario
  3. Validate template completeness
  4. Test contextualization process
  5. Gather feedback
  6. Document findings and recommendations

Acceptance Criteria:

  • Tested with tiny project scenario ✅ (Example created: templates/examples/contextualized/tiny-project/)
  • Tested with small project scenario ✅ (Example created: templates/examples/contextualized/small-project/)
  • Tested with ambitious project scenario ✅ (Example created: templates/examples/contextualized/ambitious-project/)
  • Validation report created ✅ (Examples documented in contextualization guide)
  • Improvements identified and documented ✅ (Scalability guidelines documented in contextualization guide)

E4:S06:T09 – BR-009: Improve installer discoverability and documentation​

Status: COMPLETE Priority: HIGH
Dependencies: E4:S06:T07, BR-004 fix (installer must use canonical templates, not ai-dev-kit's actual epics) ✅
Blocker: BR-004 (epic contamination must be fixed before improving discoverability) ✅
Linked BR: BR-009 (GitHub issue #14) - Installer discoverability and documentation

Input:

  • BR-009 requirements
  • Current README and installation documentation
  • Installer script (install_kanban_framework.py) from E4:S07
  • User feedback from agentic-ide-rules project

Deliverable:

  • Updated README that:

    • Prominently features install_kanban_framework.py as the primary/only installation method
    • Clearly distinguishes between:
      • Canonical epic templates (for reference)
      • ai-dev-kit's actual Kanban (example only, not for copying)
    • Includes clear examples of what users should expect after installation

  • Enhanced installation documentation:

    • Step-by-step guide using the installer
    • Examples of installation results
    • Troubleshooting guide

  • Warning mechanism (if possible):

    • Warning if users manually copy files (direct to installer)
    • Or clear documentation warning against manual copying

Approach:

  1. Update README installation section to emphasize installer
  2. Add clear distinction between canonical templates and ai-dev-kit's actual Kanban
  3. Create installation examples showing expected results
  4. Add warning/documentation about not manually copying files
  5. Update any setup guides to reference installer

Acceptance Criteria:

  • README prominently features installer as primary/only method ✅
  • README clearly distinguishes canonical templates vs. ai-dev-kit's actual Kanban ✅
  • Installation documentation includes clear examples of expected results ✅
  • Warning/documentation added about not manually copying files ✅
  • All BR-009 acceptance criteria satisfied ✅

E4:S06:T10 – BR-004: Fix epic contamination in installer​

Status: COMPLETE Priority: HIGH
Dependencies: E4:S06:T01-T02 (epic templates must exist) ✅
Blocker: None
Linked BR: BR-004 - Kanban Installation Includes Project-Specific Epics from Template

Input:

  • BR-004 requirements
  • Canonical epic templates from T01-T02 (Epics 1-21)
  • Installer script (install_kanban_framework.py) from E4:S07
  • Migration script (migrate_structure.py) from E4:S07
  • User feedback from earlution/dev-kit project

Deliverable:

  • Fixed installer that:

    • Uses canonical epic templates from packages/frameworks/kanban/templates/epics/ instead of ai-dev-kit's actual epics
    • Only installs canonical core epics (1-8, 10, 18, 22, 23) by default
    • Contextualizes Epic 1 with project name (replaces \{PROJECT_NAME\} placeholder)
    • Excludes ai-dev-kit project-specific epics (5-9 in ai-dev-kit)

  • Updated migration script to use templates

  • Verification that fresh installs only get canonical templates

Approach:

  1. Update migrate_structure.py _install_canonical_epics() to:
    • Copy from packages/frameworks/kanban/templates/epics/Epic-\{N\}-*.md templates
    • NOT copy from docs/project-management/kanban/epics/Epic-\{N\}/ (ai-dev-kit's actual epics)
    • Contextualize Epic 1 template with project name
  2. Ensure installer only installs canonical core epics (1-8, 10, 18, 22, 23)
  3. Test fresh install to verify no project-specific epics are included
  4. Update documentation to clarify template usage

Acceptance Criteria:

  • Installer uses canonical epic templates, not ai-dev-kit's actual epics ✅
  • Fresh installs only receive canonical core epics (1-8, 10, 18, 22, 23) ✅
  • Epic 1 is contextualized with project name (not "AI Dev Kit Core") ✅
  • No ai-dev-kit project-specific epics (5-9) are installed ✅
  • All BR-004 acceptance criteria satisfied ✅

Acceptance Criteria​

  • All epic templates created (Epics 1-21)
  • All story templates created (~50+ stories)
  • All task templates created (~300+ tasks)
  • Contextualization guide created with examples
  • CANONICAL_EPICS.md updated
  • Template setup guide updated
  • Structure validated with test projects
  • Documentation complete and comprehensive

Dependencies​

Blocks:

  • Proper Kanban framework installation (addresses BR-004)
  • Systematic canonical pattern management (addresses FR-005)
  • Framework adoption experience

Blocked By:

  • None (can proceed independently)

Related Work:

  • BR-004: Kanban Installation Includes Project-Specific Epics from Template
  • BR-009: Installer Discoverability and Documentation (GitHub issue #14)
  • FR-005: Systematic Canonical Epics/Stories/Tasks Template System
  • E4:S05: Canonical Epics for Kanban Framework (created initial canonical epics documentation)
  • E4:S07: Migration Support and Installation Modes (installer exists but needs better discoverability)

References​

  • packages/frameworks/kanban/templates/COMPREHENSIVE_CANONICAL_EST_STRUCTURE.md - Complete canonical structure
  • docs/documentation/engineering-and-platform/comprehensive-canonical-est-structure-design.md - Design documentation
  • packages/frameworks/kanban/templates/CANONICAL_EPICS.md - Existing canonical epics documentation
  • packages/frameworks/kanban/templates/EPIC_TEMPLATE.md - Epic template structure
  • packages/frameworks/kanban/templates/STORY_TEMPLATE.md - Story template structure
  • docs/project-management/kanban/fr-br/BR-004-kanban-installation-includes-project-specific-epics.md - Related bug report
  • docs/project-management/kanban/fr-br/BR-009-installer-discoverability-and-documentation.md - Related bug report (GitHub issue #14)
  • docs/project-management/kanban/fr-br/FR-005-systematic-canonical-epics-stories-tasks-templates.md - Related feature request

Last updated: 2025-12-09 (v0.4.6.0+1 – Task 0 complete: Story creation and comprehensive structure documentation)