Epic: Task Management — Canonical PatternStack Implementation

[dugshub]

Vision

Build a canonical, best-in-class Task Management system using PatternStack patterns. This will serve as the reference implementation for project management semantics across Stack Bench and any future CRM/PM tool PatternStack builds.

Architecture

Protocols (already exist in agentic-patterns):

• TaskProtocol — Issues/tasks with two-phase workflow (Planning → Implementation)
• ProjectProtocol — Project/milestone grouping
• SprintProtocol — Time-boxed iterations (cycles)
• CommentProtocol — Threaded discussion with reactions
• TagProtocol — Labels with semantic groups
• UserProtocol — Users and teams (read-only)
• DocumentProtocol — PRDs, specs, notes

Adapters (provider implementations):

• LinearAdapter — Reference implementation in agentic-patterns (complete)
• GitHubIssuesAdapter — NEW: Implements all protocols via GitHub REST/GraphQL API
• MockAdapter — NEW: In-memory implementation for e2e testing

Stack Bench layers:

• Features: Local DB models (EventPattern) + services for each domain
• Molecules: SyncEngine (bi-directional), TaskManagementEntity (aggregate), TaskManagementAPI (facade)
• Organisms: REST API endpoints, webhook handlers

Epics

1. Foundation — Feature-layer models, services, schemas, migrations (#EP-TM-1)
2. Provider Adapters — GitHub Issues + Mock adapters (#EP-TM-2)
3. Business Logic — Sync engine, entity aggregate, API facade (#EP-TM-3)
4. API & Integration — REST endpoints, webhooks, seeds, e2e tests (#EP-TM-4)

Semantic Model (Agile-informed)

The canonical model captures universal PM concepts:

• WorkPhase: Planning → Implementation (two-phase workflow, à la Linear)
• StatusCategory: Todo → In Progress → In Review → Done / Cancelled
• IssueType: Epic, Story, Task, Bug, Subtask
• Priority: Urgent, High, Medium, Low, None
• Relations: Parent/child, blocks/blocked-by, relates-to, duplicates
• Sprints: Time-boxed iterations with velocity tracking
• Tags: Semantic groups (issue_type, stack, work_type, state, custom)

Success Criteria

• All 7 protocols implemented for GitHub Issues
• Mock adapter passes identical test suite
• Bi-directional sync between local DB and providers
• Full REST API with CRUD for all domains
• pts quality passes (format, lint, typecheck, test)
• 80%+ test coverage on new code

[dugshub]

Sub-Issue Hierarchy Wired

All GitHub sub-issue relationships are now connected:

#118 — Master Epic (4 sub-epics)

• Epic: Task Management — Foundation (Feature Layer) #119 — Foundation (7 issues: Feature: Local Task model, service, and schemas #123, Feature: Local TaskProject model, service, and schemas #124, Feature: Local Sprint model, service, and schemas #125, Feature: Local TaskComment model, service, and schemas #126, Feature: Local TaskTag model, service, and schemas #127, Feature: Local TaskRelation model, service, and schemas #128, Feature: Alembic migrations for task management models #129)
• Epic: Task Management — Provider Adapters #120 — Provider Adapters (7 issues: Adapter: Mock adapter — full in-memory protocol implementation #130, Adapter: GitHub Issues — TaskProtocol mixin #131, Adapter: GitHub Issues — CommentProtocol mixin #132, Adapter: GitHub Issues — TagProtocol mixin #133, Adapter: GitHub Issues — ProjectProtocol + SprintProtocol mixins #134, Adapter: GitHub Issues — UserProtocol mixin + adapter composition #135, Test: Shared adapter test suite (protocol conformance) #136)
• Epic: Task Management — Business Logic (Molecules) #121 — Molecules (3 issues: Molecule: TaskManagement entity (domain aggregate) #137, Molecule: SyncEngine — bi-directional provider sync #138, Molecule: TaskManagementAPI facade #139)
• Epic: Task Management — API & Integration (Organisms) #122 — Organisms (3 issues: Organism: REST API router for task management #140, Organism: FastAPI dependencies and DI wiring #141, Organism: Seed data and E2E test suite #142)

Total: 1 master epic → 4 sub-epics → 20 implementation issues

All relationships visible in GitHub's sub-issue tracking UI.

[dugshub]

Orchestrator Log — 2026-03-24 04:45 UTC

Status: Running

Team launched with 2 parallel coordinators:

• foundation-coord — Epic 1 (Epic: Task Management — Foundation (Feature Layer) #119), working in isolated worktree. Plan approved: Task model (Feature: Local Task model, service, and schemas #123) first, then 5 features in parallel, migrations last.
• adapters-coord — Epic 2 (Epic: Task Management — Provider Adapters #120), working in isolated worktree. Building Mock adapter first, then GitHub Issues adapter.

Dependency chain:

• Epics 1 and 2 running in parallel now
• Epic 3 (Molecules) blocked on Epic 1 completion
• Epic 4 (Organisms) blocked on Epics 1, 2, 3

Sub-issue hierarchy fully wired on all 25 issues.

Next check-in: ~04:55 UTC or on significant coordinator update.

[dugshub]

Orchestrator Log — 2026-03-24 ~05:15 UTC

Epic 1 (Foundation) COMPLETE

foundation-coord delivered all 7 issues (#123-#129):

• 6 feature modules: Task, TaskProject, Sprint, TaskComment, TaskTag, TaskRelation
• 1 Alembic migration covering 7 tables
• 94 new unit tests, 348 total, all passing
• Quality gates green (format, lint, typecheck, test)
• ~35 new files

Epic 3 (Molecules) is now UNBLOCKED — depends only on Epic 1.

Epic 2 (Adapters) — Status Unknown

adapters-coord has not reported in yet. Pinging. Will respawn if unresponsive.

Next Actions

1. Launch Epic 3 coordinator (Molecules — entity, sync engine, API facade)
2. Resolve adapters-coord status
3. Epic 4 remains blocked on Epics 2 + 3

[dugshub]

Orchestrator Log — 2026-03-24 ~05:25 UTC

Epic 3 (Molecules) COMPLETE

foundation-coord delivered all 3 issues (#137-#139):

• TaskManagementEntity — domain aggregate coordinating 6 feature services, 3 business rules, 26 tests
• SyncEngine — bi-directional pull/push/full sync with protocol DTOs, 19 tests
• TaskManagementAPI — 22-method facade for REST/CLI consumption, 4 tests
• 426 total tests passing, all quality gates green

Running Totals

Epic	Status	Issues	Tests
1 Foundation	DONE	#123-#129 (7)	348
2 Adapters	IN PROGRESS	#130-#136 (7)	—
3 Molecules	DONE	#137-#139 (3)	+78 = 426
4 Organisms	BLOCKED on Epic 2	#140-#142 (3)	—

Blocker

adapters-v2 has not reported in. Previous adapters-coord also stalled. This is the critical path — Epic 4 depends on adapters. Assigning foundation-coord to pick up Epic 2 work as well.

Next Actions

1. Assign foundation-coord to start Epic 4 (Organisms) — it only truly needs the entity/facade from Epic 3, not the adapters
2. Have foundation-coord also build the Mock adapter (Adapter: Mock adapter — full in-memory protocol implementation #130) if adapters-v2 remains unresponsive
3. GitHub adapter can be done last since we have mock for testing

[dugshub]

Orchestrator Log — 2026-03-24 ~05:30 UTC

Epic 2 (Adapters) COMPLETE

adapters-v2 delivered all 7 issues (#130-#136):

• MockAdapter — 7 protocol mixins, 62+ methods, dict storage, reset()
• GitHubIssuesAdapter — full client + 6 mixins (task, comment, tag, sprint, project, user)
• Conformance test suite — 29 shared tests, MockAdapter passes all
• ~20 new files, 426 tests passing

Epic 3 (Molecules) was already COMPLETE

Current Status

Epic	Status	Issues
1 Foundation	DONE	#123-#129
2 Adapters	DONE	#130-#136
3 Molecules	DONE	#137-#139
4 Organisms	IN PROGRESS	#140-#142

Active

• foundation-coord — redirected to Epic 4 (REST API, DI wiring, seeds + E2E tests)
• adapters-v2 — completed, standing by

Remaining

Only Epic 4 left: REST API router, DI wiring, seed data, E2E tests. Then merge all worktrees.