Skip to content

Product Requirements Documents

PRDs for Finnest delivery phases, generated via the BMAD /prd workflow.

Status

1 PRD complete (Scout + Verify go-live). Subsequent PRDs written just-in-time as each delivery phase approaches.

Approach

Delivery-phase-aligned, lean format, just-in-time.

  • One PRD per delivery phase (not per module and not all up front)
  • Finnest-lean format — each PRD focuses on: Goals, Personas, User Stories + Acceptance Criteria, Success Metrics, Out of Scope, Cutover Criteria. NFRs, stack choices, constraints, and dependencies reference ../architecture/architecture.md rather than duplicating.
  • PRDs are written when the phase is next on the roadmap, not before. This follows Commandment #19 (documentation is a product — stale docs are worse than none) and avoids rot on phases that implementation will refine.

Delivery-phase view

The 44-week roadmap (per brainstorm-10 + brainstorm-11) has these delivery phases:

Phase Weeks Deliverable PRD
0 — Foundation 1–4 Empty platform with auth + agent chat Not needed (scaffolding)
Scout + Verify Go-Live 5–12 First Finnest product in ASG hands ✅ prd-scout-verify-golive.md
Migration Phase 1 — Recruitment 13–16 Full recruitment workflow on Finnest; v2 recruitment retired prd-01-migration-recruitment.md (to write Week 10)
Migration Phase 2 — Onboarding 17–20 v2 onboarding → Finnest; super onboarding wizard prd-02-migration-onboarding.md (to write Week 14)
Migration Phase 3 — Roster + CMS 21–28 Employee management + rostering on Finnest prd-03-migration-roster-cms.md (to write Week 18)
Migration Phase 4 — Timesheet + Reporting 29–36 Full platform except payroll on Finnest prd-04-migration-timesheet-reporting.md (to write Week 26)
Migration Phase X — Mobile + Pact 37–44 Flutter mobile + Pact absorption + IRAP cert prd-x-mobile-pact.md (to write Week 34)

PRD cadence: write one phase ahead. The Scout + Verify go-live PRD was written during Phase 0 (pre-roadmap start, 2026-04-16 to 2026-04-17).

Existing PRDs

prd-scout-verify-golive.md

Scope: Port Scout (recruitment) and Verify (document verification) from AgenticAI-app Laravel to Finnest/Elixir. 8-week go-live window (Weeks 5–12).

Sources: - Laravel AgenticAI-app at ../AgenticAI-app/ (154 of 169 scheduled stories completed; both domains production-complete functionally) - Architecture decisions in ../architecture/architecture.md - 12 brainstorms + 13 Finnest ADRs - Competitor gaps from brainstorm-12

Structure: - 10 epics - ~60 user stories with acceptance criteria - Out of Scope clearly bounds what's NOT in this phase - Cutover criteria for Week-8 go-live decision - Revision history v1.0 → v1.2 records cross-check corrections

Inputs for future PRDs

The /prd workflow draws from:

Format (Finnest-lean)

Every PRD in this folder follows this structure:

  1. Context & Goal — what's going live, for whom, when, why this order
  2. Strategic Context — references to architecture/brainstorms/ADRs (not re-stated)
  3. Personas — who uses what, role-scoped
  4. Success Metrics — functional + operational + commercial at phase end
  5. Epics & User Stories — grouped by user value, each story has AC
  6. Technical Constraints & Dependencies — references architecture, lists new integrations only
  7. Cutover Criteria — what must be true to declare phase complete
  8. Out of Scope — explicit deferrals with reasoning
  9. Risks & Mitigations — phase-specific risks
  10. Open Questions — decisions still pending
  11. References — cross-doc links

Each PRD is ~25–40 pages. Revision history at the bottom.

Not in scope for this folder

  • Per-module PRDs — modules are implementation units, not delivery units
  • Feature-level specs — feature surface is captured in ../research/08-master-feature-inventory.md; stories in PRDs are the user-visible manifestation per phase
  • Architectural detail — lives in ../architecture/, not here
  • Sprint-level task breakdowns — /sprint-planning output goes to ../stories/