Skip to content

AGENT_BACKLOG.md

Latest commit

 

History

History
157 lines (113 loc) · 9.05 KB

AGENT_BACKLOG.md

File metadata and controls

157 lines (113 loc) · 9.05 KB

Agent Backlog — retort

Standard backlog for tracking work items across all agent teams. This file is the single source of truth for task status during orchestrated workflows.

Table of Contents

  1. Active Sprint
  2. Backlog
  3. Completed
  4. Backlog Management Rules
  5. Priority Definitions
  6. Status Definitions

Active Sprint

Priority Team Task Phase Status Notes
P0 T4-Infrastructure Configure CI pipeline for main branch Implementation In Progress GitHub Actions workflow; scope: branch-protection, drift check, quality gates on main
P0 T10-Quality Set up test framework and coverage thresholds Ship Done Vitest + v8 coverage, 80% thresholds, json-summary reporter, wired into CI Test job
P1 T1-Backend Define core API route structure Planning In Progress REST endpoints for v1
P1 T3-Data Design initial database schema Planning Todo Depends on T1 API design
P1 T8-DevEx Configure linting and formatting rules Implementation Done ESLint + Prettier
P2 T7-Documentation Write initial ADR for tech stack decisions Discovery In Progress ADR-001 through ADR-003
P2 T2-Frontend Scaffold component library structure Planning Todo Waiting on design system
P2 T5-Auth Evaluate authentication providers Discovery Todo OAuth2 + JWT candidates
P3 T6-Integration Inventory third-party service requirements Discovery Todo Not yet scoped
P3 T9-Platform Identify shared utility functions Discovery Todo Cross-cutting concerns

Backlog

Items not yet scheduled for the active sprint.

Priority Team Task Phase Status Notes
P1 T1-Backend Implement health check endpoint Implementation Todo /api/health
P1 T3-Data Create migration tooling setup Planning Todo Prisma or Drizzle
P1 T4-Infrastructure Set up staging environment Planning Todo Docker Compose
P2 T2-Frontend Implement error boundary components Planning Todo React Error Boundary
P2 T5-Auth Implement JWT token refresh flow Planning Todo Access + refresh tokens
P2 T10-Quality Write E2E test scaffolding Planning Todo Playwright config
P3 T7-Documentation Create API documentation template Planning Todo OpenAPI/Swagger
P3 T8-DevEx Set up git hooks with Husky Implementation Todo Pre-commit + pre-push
P3 T9-Platform Create shared logging module Planning Todo Structured JSON logs
P3 T6-Integration Define webhook payload schemas Discovery Todo Event-driven patterns

Completed

Items finished in previous sprints.

Priority Team Task Phase Completed Notes
P0 T8-DevEx Initialize project repository Ship Sprint 0 Monorepo structure
P0 T4-Infrastructure Create initial Dockerfile Ship Sprint 0 Multi-stage build
P0 T7-Documentation Generate root documentation templates Ship Sprint 0 Retort sync
P1 T10-Quality Define quality gate criteria Ship Sprint 0 See QUALITY_GATES.md

Backlog Management Rules

Adding Items

  1. Any team may add items to the Backlog section at any time.
  2. New items must include all columns: Priority, Team, Task, Phase, Status, Notes.
  3. Use the Priority Definitions below to assign priority.
  4. Set the initial Phase based on how well-understood the task is.

Promoting to Active Sprint

  1. Items move from Backlog to Active Sprint during sprint planning.
  2. The orchestrator (/orchestrate) may promote items automatically when dependencies are resolved.
  3. Maximum active sprint size: 15 items across all teams.
  4. Each team should have no more than 3 active items at a time.

Moving to Completed

  1. Items move to Completed only when they reach the Ship phase and all quality gates pass.
  2. Record the sprint or date of completion in the Completed column.
  3. Completed items are retained for 4 sprints for reference, then archived.

Handling Blocked Items

  1. When a task is Blocked, add the blocker details in the Notes column.
  2. Use the format: Blocked by: T{n} - {description}.
  3. The orchestrator will attempt to resolve blockers during sync cycles.
  4. If blocked for more than one phase cycle, escalate per UNIFIED_AGENT_TEAMS.md.

Task files (optional)

When delegating work via /orchestrate, create per-task JSON files in .claude/state/tasks/ (lifecycle: submitted → accepted → working → completed/failed/rejected). The project-status dashboard uses these to report throughput, WIP count, and lead time; if the directory is empty, those metrics show as N/A.

Priority Definitions

Priority Label Definition SLA
P0 Critical Blocks all other work or affects production stability Same day
P1 High Required for current milestone; has downstream dependencies Within sprint
P2 Medium Important but not blocking; can be deferred one sprint Next sprint
P3 Low Nice to have; backlog filler; exploratory Best effort

Status Definitions

Status Description
Todo Not yet started; waiting for sprint allocation or dependencies
In Progress Actively being worked on by the assigned team
Done Completed and passed quality gates for the current phase
Blocked Cannot proceed; waiting on an external dependency or resolution

Phase Progression

Tasks move through phases as defined in UNIFIED_AGENT_TEAMS.md:

Discovery -> Planning -> Implementation -> Validation -> Ship

A task's Status resets to Todo when it advances to a new Phase, unless the team immediately begins work (then it moves to In Progress).

Cross-Team Dependencies

Track inter-team dependencies here for visibility during orchestration.

Upstream Team Downstream Team Dependency Description Status
T1-Backend T2-Frontend API contract for user endpoints Pending
T3-Data T1-Backend Database schema for user model Pending
T5-Auth T1-Backend Auth middleware interface Pending
T4-Infra T10-Quality CI pipeline for test execution Resolved
T8-DevEx All Teams Linting configuration Resolved

This backlog is maintained by Retort. Use /orchestrate to manage tasks programmatically or edit this file directly for manual adjustments.