Skip to main content
Reference — generated from the toolkit

Source of truth: toolkit/templates/pfd.md. Edit it there; this page is regenerated on build.

PFD — {product / feature name}

  • Owner (PO): …
  • SME(s): …
  • Status: draft | in review | ready (gate passed)
  • Version: 0.1.0

Problem & jobs-to-be-done​

What problem, for whom, and the job they're hiring this to do. Evidence, not assertion.

Personas​

The people who use or are affected by this. Keep to those that change design decisions.

Scope​

  • In scope: …
  • Out of scope: … (explicit — this is where ambiguity hides)

Domain rules​

Reference the domain brief for the full rules and edge cases. Summarise the load-bearing ones here.

Acceptance criteria​

Per the acceptance-criteria standard: Given/When/Then, three examples per rule (positive / negative / boundary), no banned vague words.

Success metrics​

Testable measures of whether this worked. Numbers with definitions.

Non-functional requirements​

Selected from the NFR & compliance catalogue (to follow) — ISO/IEC 25010 targets, WCAG 2.2 AA, data residency, availability/RPO/RTO, audit-trail, tenant isolation.

Compliance constraints​

UK GDPR, FCA Consumer Duty, EU AI Act classification (if the feature uses AI), and any market-specific rules.

Commercial section (Commercial signs off before Definition exits)​

Target segments, pricing/packaging hypotheses, positioning.

Glossary​

Link to the product's [ubiquitous-language glossary]; every domain term used above resolves there — no orphan terms.

Open questions​

Triaged blocking vs non-blocking. No blocking questions may remain at the gate.