Skip to content
This project is under active development and subject to breaking changes. See the changelog for release notes.

Work Items

The board is the source of truth for task status, assignment, and workflow state. Design decisions and specifications remain authoritative as disk artifacts (specs, ADRs, plan.md). Local files (tasks.md, structure.md) are caches. Agents integrate with GitHub Issues and Azure DevOps for bidirectional work item management.

Auto-detected from git remote URL by the detect-repo-platform.sh sessionStart hook:

Remote PatternPlatform
github.comGitHub Issues
dev.azure.com / visualstudio.comAzure DevOps

Configuration saved to .memory/board-config.md.

TypeLabelTitle Format
Epicepic[Epic] NAME
Featurefeature[Feature] NAME
User Storytype:user-story[FEATURE] DESCRIPTION
Tasktype:task[FEATURE] DESCRIPTION
ADRtype:adr[ADR] DOMAIN
Tech Debttype:tech-debt[Tech Debt] DESCRIPTION

Hierarchy uses sub-issues for parent-child relationships.

Always applied to every work item:

  • copilot-generated: Marks AI-created items
  • ai-model:MODEL_NAME: AI model traceability

Additional by type:

TypeAdditional Tags
User Storytype:user-story, feature:NAME, priority:{p1,p2,p3}
Tasktype:task, feature:NAME, phase:PHASE
Epicepic
Featurefeature, priority:{p1,p2,p3}
flowchart LR
  A["Select Task"] --> B["Assign to Self"]
  B --> C["In Progress"]
  C --> D["Open PR"]
  D --> E["Close on Merge"]
  E --> F["Sync Board"]
  F -->|"all children done?"| G["Cascade Close Parent"]

Cascade closure: When all children complete, the agent proposes closing the parent (user story, then feature, then epic).

flowchart TD
  Epic["Epic"]
  F1["Feature A"]
  F2["Feature B"]
  US1["User Story P1"]
  US2["User Story P2"]
  US3["User Story P1"]
  T1["Task"]
  T2["Task"]
  T3["Task"]
  T4["Task"]

  Epic --> F1
  Epic --> F2
  F1 --> US1
  F1 --> US2
  F2 --> US3
  US1 --> T1
  US1 --> T2
  US2 --> T3
  US3 --> T4

Tasks labeled copilot-candidate are suitable for autonomous AI execution:

DelegableNot Delegable
CRUD endpoints per specInitial project setup
Validations per specExternal integrations
Service following contractPublic API changes
Unit tests following patternMulti-module refactoring