Skip to main content

Task Naming Migration Guide

Date: 2025-12-04
Change: Task naming format changed from Exx:Sxx:Txxx (3-digit task) to Exx:Sxx:Txx (2-digit task)
Policy: packages/frameworks/kanban/policies/kanban-governance-policy.md

Summary​

The Kanban Task naming policy has been updated to always use the full Exx:Sxx:Txx format with 2-digit task numbers (instead of 3-digit). Tasks are NEVER referenced as standalone Txxx or Txx - they must always include the Epic and Story context: E\{epic\}:S\{story\}:T\{task\}.

Format Change​

Old Format:

  • Exx:Sxx:Txxx (Epic, Story, Task with 3-digit zero padding)
  • Example: E20:S07:T10 = Epic 20, Story 7, Task 10

New Format:

  • Exx:Sxx:Txx (Epic, Story, Task with 2-digit zero padding)
  • Example: E20:S07:T10 = Epic 20, Story 7, Task 10

Migration Strategy​

Backward Compatibility​

Existing Tasks:

  • Existing tasks can keep their current format (backward compatible)
  • No requirement to rename existing task files
  • No requirement to update existing task references in completed work

New Tasks:

  • All new tasks MUST use full Exx:Sxx:Txx format (2-digit task number)
  • Task files should be named T01-*.md, T02-*.md, etc. (for file naming only)
  • Task IDs in commits and references MUST use full Exx:Sxx:Txx format (e.g., E1:S01:T01, E2:S04:T05)
  • NEVER use standalone T01 or T001 - always include Epic and Story context

Transition Period​

During Transition:

  • Both formats are acceptable for existing tasks
  • New tasks MUST use full Exx:Sxx:Txx format (2-digit task)
  • Documentation should be updated to show Exx:Sxx:Txx format
  • Examples should use Exx:Sxx:Txx format

After Transition:

  • All new work uses full Exx:Sxx:Txx format (2-digit task)
  • Documentation consistently uses Exx:Sxx:Txx format
  • Examples use Exx:Sxx:Txx format
  • No standalone Txx or Txxx references - always include Epic and Story

What Was Updated​

Policy Documents​

  • ✅ packages/frameworks/kanban/policies/kanban-governance-policy.md
  • ✅ packages/frameworks/numbering & versioning/kanban-governance-policy.md
  • ✅ docs/project-management/rituals/policy/kanban-governance-policy.md

Templates​

  • ✅ packages/frameworks/kanban/templates/STORY_TEMPLATE.md
  • ✅ packages/frameworks/kanban/templates/EPIC_TEMPLATE.md

Examples​

  • ✅ packages/frameworks/kanban/examples/Story-33-Example.md
  • ✅ packages/frameworks/kanban/examples/Epic-4-Example.md
  • ✅ packages/frameworks/kanban/integration/numbering-versioning-integration.md
  • ✅ packages/frameworks/kanban/README.md
  • ✅ packages/frameworks/workflow mgt/docs/documentation/Developer_Docs/vwmp/release-workflow-agent-execution.md
  • ✅ packages/frameworks/workflow mgt/docs/documentation/templates/action-workflow-template.md
  • ✅ packages/frameworks/workflow mgt/docs/documentation/Developer_Docs/vwmp/release-workflow-reference.md
  • ✅ packages/frameworks/workflow mgt/docs/architecture/standards-and-adrs/versioning-strategy.md
  • ✅ packages/frameworks/kanban/guides/portfolio-kanban-alignment-playbook.md
  • ✅ packages/frameworks/kanban/FR_BR_INTAKE_AGENT_GUIDE.md
  • ✅ packages/frameworks/kanban/FR_BR_INTAKE_GUIDE.md

Code/Scripts​

  • ✅ No scripts found that parse Task IDs with Txxx format
  • ✅ No validators found that check Task format specifically

Examples​

Task Checklist Format​

Old:

- [x] **E2:S02:T01 – Add CHECK Phase** ✅ COMPLETE (v0.2.2.1+1)
- [ ] **E2:S02:T02 – Add ACT Phase**

New:

- [x] **E2:S02:T01 – Add CHECK Phase** ✅ COMPLETE (v0.2.2.1+1)
- [ ] **E2:S02:T02 – Add ACT Phase**

Task File Naming​

Old:

T001-add-check-phase.md
T002-add-act-phase.md
T010-some-task.md

New:

T01-add-check-phase.md
T02-add-act-phase.md
T10-some-task.md

Commit Message References​

Old:

Release v0.2.2.1+1: E2:S02:T01: Add CHECK Phase

New:

Release v0.2.2.1+1: E2:S02:T01: Add CHECK Phase

Impact on Version Numbers​

No Impact:

  • Version numbers use numeric Task component: RC.EPIC.STORY.TASK+BUILD
  • Task component in version is numeric (e.g., 0.2.2.1+1 = Task 1)
  • Task naming format (Txx vs Txxx) does not affect version numbers
  • Version numbers remain unchanged

Example:

  • Task T01 (new format) = Version 0.2.2.1+1 (Task component = 1)
  • Task T001 (old format) = Version 0.2.2.1+1 (Task component = 1)
  • Both refer to the same Task number, just different display format

Best Practices​

  1. Use Full Exx:Sxx:Txx Format for All Task References:

    • All task references MUST use full Exx:Sxx:Txx format (2-digit task number)
    • Task files: T01-*.md, T02-*.md, etc. (file naming only - still use full format in content)
    • Task IDs in documentation: E2:S02:T01, E2:S02:T02, etc.
    • NEVER use standalone T01 or T001 - always include Epic and Story context

  2. Maintain Existing Tasks:

    • Existing tasks can keep their format
    • No need to rename existing files
    • No need to update historical references

  3. Update Documentation:

    • New documentation should use Txx format
    • Examples should use Txx format
    • Templates should use Txx format

  4. Consistency:

    • Use consistent format within a story
    • Use consistent format in documentation
    • Use consistent format in examples

References​

  • Kanban Policy: packages/frameworks/kanban/policies/kanban-governance-policy.md
  • Versioning Policy: packages/frameworks/numbering & versioning/kanban-governance-policy.md
  • Dev-Kit Policy: docs/project-management/rituals/policy/kanban-governance-policy.md
  • Task T07: docs/project-management/kanban/epics/Epic-2/Story-002-pdca-integration-into-release-workflow/T07-implement-task-naming-change.md
  • Task T08: docs/project-management/kanban/epics/Epic-2/Story-002-pdca-integration-into-release-workflow/T08-update-kanban-docs-to-txx-standard.md

Questions?​

If you have questions about the migration or need clarification, refer to:

  • Task T07: Implementation details
  • Task T08: Documentation updates
  • Kanban policy documents: Current standards