← Retour
W

write-back-office-prd

active
Rédige une spécification fonctionnelle exhaustive d'un outil interne à partir de tous les documents du projet

skill procédurale

Procédure
# Write Back-Office PRD

Turn everything known about an internal B2B tool into an exhaustive functional specification agents build from without re-asking. Not a lean brief: every process, every screen, every table and chart, the data model, the stack and libraries, down to the PDF models. Our specs run past 60 pages. Nothing is left implicit.

Method in one line: read everything -> write the brief that opens the questions -> grill-me to answer them -> write the exhaustive PRD -> full re-read where every observation re-opens grill-me, until complete coherence.

Golden rules:
- Exhaustive, not short. Every subject named becomes a fully defined process.
- Nothing invented. Every fact is grounded in a source or a grill-me answer; unknowns are [TO CLARIFY].
- Standardize by reference. For anything standardized (libraries, design, e-invoicing, auth/RBAC, security), the PRD says WHAT and references the owning skill/agent for HOW.

Phases:
0. Read every document in the folder, insisting on video-call transcripts and the initial brief we write.
1. Write the brief: each mention of a subject opens a complete definition process for that subject.
2. grill-me, one question at a time, to close every open question.
3. Write module by module: flux, each view field-by-field, each table and chart with its formulas, the data model, the stack and libraries (by reference), the PDF models, V1 phasing.
4. French B2B: e-invoicing trigger, reference /add-e-invoicing.
5. Client projects: delivery & reversibility.
6. Full re-read: every observation re-opens grill-me, loop until a pass yields zero observation.

Stop when:
[ ] A full re-read produces zero observation.
[ ] Every named subject has a complete definition.
[ ] Every view, table and formula is specified.
[ ] An agent can build any module without re-asking.

Anti-patterns:
✗ A lean 2-4 page brief; a mention without a defined process.
✗ Re-explaining a standardized method instead of referencing it.
✗ Inventing a figure, status or formula.
✗ Reading a sample of the folder, skipping the transcripts.
✗ Shipping without the full re-read loop.
Déclencheurs
rédige un PRD / write the PRDspecs produit d'un outil interne ou ERPcadrer un back-office avant développementformaliser une spécification depuis les documents projet
Métriques

invocations

latency p50

latency p95

tokens in

tokens out

error rate