Skip to content

Sprint Stories

Sprint backlogs and individual story files, generated via the BMAD /sprint-planning workflow.

Status

Phase 0 complete as of 2026-04-17. 19 stories across 4 sprints covering Weeks 1–4 of the 44-week roadmap (STORY-F-010 retired 2026-04-18 per ADR-016-F). Scout + Verify go-live sprint planning scheduled for 2026-05-08 (Week 3 of Phase 0) with execution signal from Phase 0 sprints informing capacity.

Current artefacts

  • sprint-plan-finnest-phase-0-2026-04-17.md — Phase 0 sprint plan (4 sprints, 50 points, 19 stories)
  • sprint-status.yaml — BMAD v6.0 canonical sprint state (mirrors AgenticAI-app docs/sprint-status.yaml shape)
  • STORY-F-001.md through STORY-F-020.md — individual story files (one per sprint-allocated story)

Structure

Flat story files in this folder (matching AgenticAI-app _bmad-output/stories/ pattern). Stories are NOT migrated to the code repo — per the user's preference, planning artefacts stay in planning repo permanently.

stories/
├── sprint-plan-finnest-phase-0-2026-04-17.md      # master Phase 0 plan
├── sprint-plan-finnest-scout-verify-TBD.md         # will land Week 3 of Phase 0
├── sprint-status.yaml                              # canonical sprint tracker
├── STORY-F-001.md                                  # 20 individual story files
├── STORY-F-002.md
├── ...
├── STORY-F-020.md
├── phase-0-retro-2026-05-15.md                    # end-of-Phase-0 retro (created on execution)
└── README.md                                       # this file

Story file format

Every story file follows the BMAD template:

  • User story (As a / I want / So that)
  • Background / scope / technical notes
  • Dependencies
  • Acceptance criteria (specific, testable — no "works correctly")
  • Testing requirements
  • References (architecture docs, ADRs, brainstorms, guardrails)

Story ID convention

STORY-F-NNN — F prefix distinguishes Finnest stories from AgenticAI-app stories (STORY-NNN) when the two are referenced together during Strangler Fig migration.

Phase 0 summary

Sprint Week Goal Stories Points
1 1 Umbrella + local dev + CI F-001 – F-005 12
2 2 Decision gate: auth + tenant + V2Repo + integration deploy F-006 – F-009 11
3 3 Agents + MCP + compliance seed + deploy pipeline F-011 – F-015 14
4 4 Event store + Agent Chat UI + Cmd+K + staging/prod deploy + smoke test F-016 – F-020 13
Total 4 weeks Phase 0 deliverable 19 50

Week 2 decision gate (end of Sprint 2) determines whether Elixir Direct go-live continues or Plan B Laravel-ship triggers.

Upcoming phases (not yet planned)

Phase Weeks Planning trigger Prd path
Scout + Verify Go-Live 5–12 Week 3 of Phase 0 (2026-05-08) ../prd/prd-scout-verify-golive.md
Migration Phase 1 — Recruitment 13–16 Week 10 of roadmap (write-ahead per prd/README.md)
Migration Phase 2 — Onboarding 17–20 Week 14 (write-ahead per prd/README.md)
Migration Phase 3 — Roster + CMS 21–28 Week 18 —
Migration Phase 4 — Timesheet + Reporting 29–36 Week 26 —
Migration Phase X — Mobile + Pact 37–44 Week 34 —

Sprint cadence

  • Length: 1 week (Mon–Fri working days; ~5 working days per sprint)
  • Capacity: 15 points per sprint (Gautham + AI assistance)
  • Target velocity: ~13 points (buffer for Elixir learning curve, unknowns, bugs)
  • Ceremony: kickoff Monday, review/retro Friday (informal; solo dev = lightweight)

Inputs for future sprint planning

Definition of Done (per story, per sprint)

See sprint plan §Definition of Done or sprint-status.yaml definition_of_done key:

  • Code + tests + format + credo + dialyzer + sobelow + deps.audit + boundary all green
  • Architecture tests still passing
  • All ACs in story file ticked
  • sprint-status.yaml updated
  • Commit references story ID (STORY-F-NNN: short message)