stepsCompleted: ["step-01-document-discovery", "step-02-prd-analysis", "step-03-epic-coverage-validation", "step-04-ux-alignment", "step-05-epic-quality-review", "step-06-final-assessment"] documentInventory: prd: prd.md architecture: architecture.md epics: epics.md
Date: 2026-02-27 Project: agentMarketing
Workspace & Account Management
Contributor Management
AI Education & Use Case Library
Idea Submission
AI Enrichment & Scoring
Backlog & Idea Management
Qualification & Communication
Prioritization
Export & Sharing
Compliance & Data
Total FRs: 47 (FR0, FR1–FR38, including FR3b, FR14-IA1 through FR14-IA6, FR18b)
Performance
Availability & Reliability
Cost & LLM Scalability
Security & Data
LLM Output Quality
Total NFRs: 18 (NFR1–NFR18)
The PRD is well-structured and thorough. Key strengths:
Potential areas to watch during epic validation:
| FR Number | PRD Requirement (short) | Epic Coverage | Status |
|---|---|---|---|
| FR1 | Création workspace | Epic 1 - Story 1.3 | ✅ Covered |
| FR2 | Onboarding guidé | Epic 1 - Story 1.5 | ✅ Covered |
| FR3 | Configuration workspace (secteur, taille) | Epic 1 - Story 1.4 | ✅ Covered |
| FR3b | Contextualisation LLM via secteur/taille | Epic 1 - Story 1.4 | ✅ Covered |
| FR4 | Limites tier Free | Epic 1 - Story 1.6 | ✅ Covered |
| FR5 | Affichage niveau abonnement | Epic 1 - Story 1.6 | ✅ Covered |
| FR6 | Invitation contributeurs par email | Epic 2 - Story 2.1 | ✅ Covered |
| FR7 | Email lien direct formulaire | Epic 2 - Story 2.1 | ✅ Covered |
| FR8 | Accès formulaire sans compte | Epic 2 - Story 2.2 | ✅ Covered |
| FR9 | Liste contributeurs + statut | Epic 2 - Story 2.9 | ✅ Covered |
| FR10 | Relance automatique J+21 | Epic 2 - Story 2.10 | ✅ Covered |
| FR11 | Relance manuelle Transformateur | Epic 2 - Story 2.11 | ✅ Covered |
| FR12 | Personnalisation message relance | Epic 2 - Story 2.11 | ✅ Covered |
| FR13 | Confirmation avant envoi relance | Epic 2 - Story 2.11 | ✅ Covered |
| FR14-IA1 | Exemples IA contextuels (LLM) | Epic 2 - Story 2.3 | ✅ Covered |
| FR14-IA2 | Exemples sans jargon technique | Epic 2 - Story 2.3 | ✅ Covered |
| FR14-IA3 | Bibliothèque accessible depuis formulaire | Epic 2 - Story 2.4 | ✅ Covered |
| FR14-IA4 | Adoption cas → pré-remplissage formulaire | Epic 2 - Story 2.4 | ✅ Covered |
| FR14-IA5 | CDO accès bibliothèque + lien partageable | Epic 2 - Story 2.4 | ✅ Covered |
| FR14-IA6 | Bibliothèque min 5 cas/secteur + 5 cas/fonction | Epic 2 - Story 2.4 | ✅ Covered |
| FR14 | Formulaire soumission 5 champs | Epic 2 - Story 2.2 | ✅ Covered |
| FR15 | Soumission par email | Epic 2 - Story 2.5 | ✅ Covered |
| FR16 | Confirmation visuelle soumission | Epic 2 - Story 2.7 | ✅ Covered |
| FR17 | Pièces jointes (types, tailles, max 3) | Epic 2 - Story 2.6 | ✅ Covered |
| FR18 | Enrichissement LLM post-soumission | Epic 3 - Story 3.1 | ✅ Covered |
| FR18b | Explication LLM en langage non-technique | Epic 3 - Story 3.1 | ✅ Covered |
| FR19 | Scores + explication enrichie visibles CDO | Epic 3 - Story 3.4 | ✅ Covered |
| FR20 | Ajustement manuel des scores (tracé) | Epic 3 - Story 3.4 | ✅ Covered |
| FR21 | Fallback LLM + indicateur + retry manuel | Epic 3 - Story 3.1 | ✅ Covered |
| FR22 | Vue liste triable | Epic 3 - Story 3.2 | ✅ Covered |
| FR23 | Vue kanban 4 colonnes | Epic 3 - Story 3.3 | ✅ Covered |
| FR24 | Filtrage backlog | Epic 3 - Story 3.2 | ✅ Covered |
| FR25 | Fiche détaillée idée | Epic 3 - Story 3.4 | ✅ Covered |
| FR26 | Changement de statut + Non prioritaire | Epic 3 - Story 3.5 | ✅ Covered |
| FR27 | Recherche mots-clés backlog | Epic 3 - Story 3.6 | ✅ Covered |
| FR28 | Résumé nouvelles activités | Epic 3 - Story 3.7 | ✅ Covered |
| FR29 | Question de qualification | Epic 4 - Story 4.1 | ✅ Covered |
| FR30 | Notification email question de qualification | Epic 4 - Story 4.1 | ✅ Covered |
| FR31 | Réponse contributeur à qualification | Epic 4 - Story 4.2 | ✅ Covered |
| FR32 | Notification email Transformateur (nouvelle idée) | Epic 3 - Story 3.8 | ✅ Covered |
| FR33 | Drag & drop priorisation | Epic 4 - Story 4.3 | ✅ Covered |
| FR34 | Classement de priorité visible | Epic 4 - Story 4.3 | ✅ Covered |
| FR35 | Export PDF | Epic 4 - Story 4.4 | ✅ Covered |
| FR36 | Lien partageable lecture seule | Epic 4 - Story 4.5 | ✅ Covered |
| FR37 | Mention RGPD sur formulaire | Epic 2 - Story 2.8 | ✅ Covered |
| FR38 | Suppression données sur demande | Epic 4 - Story 4.6 | ✅ Covered |
| NFR | Description (short) | Referenced in Story | Status |
|---|---|---|---|
| NFR1 | Formulaire < 2s (95%) | Not explicitly in any story AC | ⚠️ Implicit only |
| NFR2 | Confirmation < 1s | Story 2.7 | ✅ Covered |
| NFR3 | Exemples LLM < 3s + fallback | Story 2.3 | ✅ Covered |
| NFR4 | Enrichissement < 10s / fallback > 30s | Story 3.1 | ✅ Covered |
| NFR5 | Backlog < 3s (≤ 200 idées) | Story 3.2 | ✅ Covered |
| NFR6 | Ingestion email < 15 min | Story 2.5 | ✅ Covered |
| NFR7 | Disponibilité 99%/mois | Infrastructure - no story | ⚠️ Not in any story |
| NFR8 | Taux échec LLM < 5%, alerte | No story | ⚠️ Not in any story |
| NFR9 | Formulaire fonctionnel si LLM down | Story 2.3 (fallback) | ✅ Partially covered |
| NFR10 | Coût LLM ≤ 0,05€/idée | No story | ⚠️ Not in any story |
| NFR11 | Limite 30 idées LLM (tier Free) | Story 1.6 (FR4/FR5) implicit | ⚠️ Implicit only |
| NFR12 | 50 appels LLM/mois tier Free (serveur) | Story 1.6 (FR4/FR5) implicit | ⚠️ Implicit only |
| NFR13 | Hébergement EU | Architecture constraint - no story | ⚠️ Not in any story |
| NFR14 | Isolation workspace (incl. prompts LLM) | Story 1.2 (schema multi-tenant) partial | ⚠️ Partially covered |
| NFR15 | Pièces jointes chiffrées AES-256 | Story 2.6 | ✅ Covered |
| NFR16 | HTTPS/TLS 1.2+ | Infrastructure - no story | ⚠️ Not in any story |
| NFR17 | Indicateur "générique" si secteur non configuré | Story 2.3 (fallback) partial | ⚠️ Partially covered |
| NFR18 | Label "Suggestion IA - à ajuster" | Story 3.4 | ✅ Covered |
None - all 46 PRD FRs are covered in epics and stories.
The following NFRs have no dedicated story or explicit acceptance criteria. This is a common pattern for infrastructure-level NFRs, but some are significant enough to warrant attention:
Found - ux-design-specification.md (45 KB, 27/02/2026), complete 14-step workflow.
The UX spec covers: executive summary, target users, design challenges, design system (Tailwind + shadcn/ui + Livinia Chaleureux palette), responsive strategy, accessibility (WCAG 2.1 AA), component library (6 custom components defined), user journey flows (J1, J2, J2b, J3), UX consistency patterns, emotional design, and competitive benchmarking.
Well-Aligned Areas:
| UX Spec Element | PRD Requirement | Status |
|---|---|---|
| DepartmentPicker + ExamplePill avant le formulaire | FR14-IA1 (exemples contextuels selon secteur + département) | ✅ Aligned |
| Label "Suggestion IA - à ajuster" systématique | NFR18 | ✅ Aligned |
| Fallback LLM immédiat < 3s / < 10s | NFR3, NFR4, NFR9 | ✅ Aligned |
| StatusStepper (Envoyé → En traitement → À l'ordre du jour) | FR26 (statuts contributeur) | ✅ Aligned |
| Confirmation visuelle < 1s | NFR2, FR16 | ✅ Aligned |
| Empty state rassurant (backlog vide J1-J3) | PRD Journey 1 (implicit) | ✅ Aligned |
| Drag & drop (dnd-kit) | FR33, FR34 | ✅ Aligned |
| Export en position primaire | FR35 | ✅ Aligned |
| Desktop-first, mobile form | PRD MVP feature #20 | ✅ Aligned |
| WCAG 2.1 AA | Architecture NFR constraint | ✅ Aligned |
UX Additions Beyond PRD - Gaps to Address:
| UX Spec Requirement | PRD Coverage | Gap Level |
|---|---|---|
| Email de confirmation au contributeur après soumission (avec CTA "Soumettre une autre idée") | Not in PRD FRs. FR16 only covers visual confirmation (in-app). | ⚠️ NOTABLE - UX adds an email confirmation not in PRD nor in any story. Should be added as AC to Story 2.7 or as a new story. |
| Vue "Cartes" (grid cards) comme 3ème vue backlog | PRD has FR22 (liste) + FR23 (kanban) - only 2 views. UX direction 2 adds a card grid view. | ⚠️ SCOPE ADDITION - Card grid view is defined in UX design directions but no corresponding FR or epic story covers it. Needs resolution: include in Story 3.2 or explicitly defer to post-MVP. |
| DepartmentPicker à l'ouverture si département inconnu (1 clic avant exemples) | FR14-IA1 says "si le département est connu, les exemples sont filtrés par fonction" - implies it might be unknown but doesn't specify the UX flow to ask for it. | ⚠️ UX DETAIL - The department picker interaction is not in any story AC. Should be added to Story 2.3. |
| Rappel J+30 au contributeur ("pas de signal revenir soumettre" mitigation) | Not in PRD FRs. Growth features include "notifications email contributeur enrichies" but J+30 reminder is not defined in MVP scope. | ℹ️ LOW - Pre-mortem mitigation in UX; not confirmed as MVP scope. Mark as out-of-scope until PRD is updated. |
| Tooltip sur chaque champ enrichi + indicateur de confiance (pre-mortem mitigation) | Partially in PRD: NFR18 (label "Suggestion IA") + FR20 (ajustement possible). Tooltips not explicitly specified. | ℹ️ LOW - Implementation detail; acceptable as developer discretion within the spirit of NFR18. |
Well-Aligned Areas:
| UX Requirement | Architecture Support | Status |
|---|---|---|
| Tailwind + shadcn/ui + Livinia Chaleureux | Explicitly specified in architecture decision | ✅ Aligned |
| dnd-kit for drag & drop (kanban + backlog) | Explicitly listed in frontend architecture decisions | ✅ Aligned |
DepartmentPicker, ExamplePill, IdeaCard, AIBadge, ScoreSlider, KanbanBoard, EmptyState, StatusStepper |
Architecture's components/form/, components/backlog/, components/idea/ cover all UX components (some naming differs slightly: ExamplesPanel.tsx vs. ExamplePill) |
✅ Aligned (minor naming delta - not a blocker) |
| 2 interfaces asymétric (CDO dense / contributeur épuré) | Architecture separation: (dashboard)/ for CDO, (public)/submit/ for contributor |
✅ Aligned |
| LLM fallback (skeleton → generics) | Architecture's services/llm.ts with fallback, skeleton pattern documented |
✅ Aligned |
| WCAG 2.1 AA | Architecture lists Radix UI under shadcn/ui; ARIA documented in UX spec; explicitly referenced in architecture | ✅ Aligned |
| Route for share link | Architecture has app/share/[shareToken]/page.tsx |
✅ Aligned |
| Breakpoints (sm:640, md:768, lg:1024, xl:1280) | Architecture references same breakpoints from UX spec | ✅ Aligned |
Architecture Gaps vs UX:
| UX Requirement | Architecture Gap | Gap Level |
|---|---|---|
| Card grid view (direction 2) | Not present in architecture's component list or routing structure | ⚠️ MINOR - If card view is confirmed in-scope, need to add components/backlog/CardGrid.tsx and update Story 3.2 |
| Email confirmation to contributor post-submission | services/email.ts exists but no explicit route/procedure for this email |
⚠️ MINOR - Needs explicit addition to email.ts + Story 2.7 |
| LLM error rate monitoring (NFR8) | Architecture notes it as a "nice-to-have" - no monitoring service or alerting defined | ⚠️ MINOR - Acceptable for MVP launch, but should be planned for early post-launch |
Email confirmation after submission is a missing story: The UX spec explicitly includes an email to the contributor after submission (with CTA to submit another idea). This is not an FR in the PRD and not in any story AC. Without it, the "boucle de retour" for the contributor is broken. Recommendation: Add AC to Story 2.7 or create Story 2.7b.
Card grid view (Vue Cartes) has no story: The UX spec introduces a third backlog view (card grid). The PRD only defines FR22 (list) + FR23 (kanban). This is a scope addition with no story. Recommendation: Either defer explicitly to post-MVP or add story in Epic 3.
DepartmentPicker flow not explicit in Story 2.3: The UX spec's J2 flow shows that if the department is unknown, a department picker is shown BEFORE examples are generated. This interaction is critical for FR14-IA1 accuracy but not in any story AC. Recommendation: Add explicit AC to Story 2.3.
Architecture's ExamplesPanel.tsx vs. UX's ExamplePill + DepartmentPicker split: The architecture bundles both into one file, while UX spec defines two distinct components. Minor naming inconsistency - no blocker, but developer should follow UX spec decomposition for clarity.
Overall UX Alignment: GOOD - The UX spec is detailed, well-aligned with PRD and Architecture. Three notable additions (email confirmation, card grid view, department picker flow) need explicit story coverage or deferral decisions before implementation starts.
4 epics, 23 stories reviewed against create-epics-and-stories best practices.
User Value Focus: ✅ PASS (with caveat)
Epic Independence: ✅ PASS - Epic 1 stands alone completely.
Story Dependencies within Epic 1:
| Story | Dependencies | Valid? |
|---|---|---|
| 1.1 (scaffold) | None | ✅ Independent |
| 1.2 (schema) | 1.1 (T3 project with Prisma) | ✅ Valid backward |
| 1.3 (FR1 create workspace) | 1.1 + 1.2 | ✅ Valid backward |
| 1.4 (FR3 config secteur/taille) | 1.3 (workspace exists) | ✅ Valid backward |
| 1.5 (FR2 onboarding) | 1.3 + 1.4 | ✅ Valid backward |
| 1.6 (FR4/FR5 tiers) | 1.3 | ✅ Valid backward |
🟡 Minor Concern - Story 1.5 forward reference: Story 1.5's onboarding checklist includes step "inviter des contributeurs" (Epic 2 feature) and "soumettre une 1ère idée" (also needs Epic 2 form). The checklist UI can be built, and steps will show as "pending" since the underlying features don't exist yet. This is acceptable if the ACs are interpreted as: the checklist renders correctly and marks steps complete when the actions are eventually performed. However, the AC "les étapes sont skipables sauf la configuration de base" implies interaction - which needs the steps to be functional. Recommendation: Add AC clarification that checklist items show "À venir" state until the underlying feature of a later epic is deployed.
Acceptance Criteria Quality - Epic 1:
User Value Focus: ✅ PASS - Clearly user-centric, delivers core contributor and Transformateur workflows.
Epic Independence: ✅ PASS - Functions using only Epic 1 output.
Story Dependencies within Epic 2:
| Story | Dependencies | Valid? |
|---|---|---|
| 2.1 (invitation FR6/FR7) | Epic 1 workspace | ✅ |
| 2.2 (form FR8/FR14) | Epic 1 workspace | ✅ |
| 2.3 (examples FR14-IA1/IA2) | 2.2 (form exists), Epic 1 LLM config | ✅ |
| 2.4 (library FR14-IA3 to IA6) | Epic 1 workspace | ✅ |
| 2.5 (email ingestion FR15) | Epic 1 workspace, email webhook | ✅ |
| 2.6 (attachments FR17) | 2.2 (form) | ✅ Valid backward |
| 2.7 (confirmation FR16) | 2.2 (form) | ✅ Valid backward |
| 2.8 (RGPD FR37) | 2.2 (form) | ✅ Valid backward |
| 2.9 (contributor list FR9) | 2.1 (invitations) | ✅ Valid backward |
| 2.10 (auto relance FR10) | 2.1 (invitations) | ✅ Valid backward |
| 2.11 (manual relance FR11-13) | 2.1 (invitations) | ✅ Valid backward |
🟠 Major Issue - Story 2.2 forward dependency on Story 2.6: Story 2.2 acceptance criteria explicitly includes "pièces jointes optionnelles" as one of the 5 form fields: "When je remplis les champs (description problème, département, impact estimé, fréquence, pièces jointes optionnelles)." But the actual attachment implementation (upload, file type validation, storage path) is in Story 2.6.
🟠 Major Issue - Story 2.4 oversized (potential): Story 2.4 bundles 4 FRs (FR14-IA3, FR14-IA4, FR14-IA5, FR14-IA6) including:
The content creation requirement (FR14-IA6) is significant and distinct from the technical implementation. Bundling seed data creation with the technical library feature in one story risks a very large story that could block an entire sprint.
🟡 Minor Concern - Story 2.10 settings reference:
Story 2.10 AC: "la relance automatique peut être désactivée par le Transformateur dans les paramètres du workspace." No story explicitly creates a workspace settings page with this toggle. The settings page is implied in the architecture (workspace/[workspaceId]/settings/page.tsx) but no story covers it. If Story 2.10 requires this settings toggle to be built, it creates an implicit dependency on an unspecified story. Recommendation: Add a brief story or sub-task within Epic 1 Story 1.4 or Story 1.6 to create the workspace settings page scaffold, or add the relance toggle as an AC to Story 1.6.
Acceptance Criteria Quality - Epic 2:
User Value Focus: ✅ PASS - Core CDO workflow, clearly user-centric.
Epic Independence: ✅ PASS - Functions using Epic 1 + 2 output (needs ideas submitted).
Story Dependencies within Epic 3:
| Story | Dependencies | Valid? |
|---|---|---|
| 3.1 (enrichissement FR18/18b/21) | Ideas submitted (Epic 2), LLM service | ✅ |
| 3.2 (liste FR22/24) | Ideas exist (Epic 2) | ✅ |
| 3.3 (kanban FR23) | 3.2 or ideas exist | ✅ |
| 3.4 (fiche FR25/19/20) | Ideas exist, enrichment (3.1) | ✅ Valid backward |
| 3.5 (statuts FR26) | Ideas exist | ✅ |
| 3.6 (recherche FR27) | Ideas exist | ✅ |
| 3.7 (résumé activités FR28) | Ideas exist + ⚠️ | ⚠️ See below |
| 3.8 (notification FR32) | Ideas exist + email service | ✅ |
🟠 Major Issue - Story 3.7 forward dependency on Epic 4: Story 3.7 AC: "je vois un résumé des nouvelles idées et des réponses reçues aux questions de qualification." The "réponses reçues" part requires the qualification feature from Epic 4 (Stories 4.1/4.2) to exist.
Acceptance Criteria Quality - Epic 3:
User Value Focus: ✅ PASS - User-centric, covers critical CDO and contributor workflows.
Epic Independence: ✅ PASS - Functions using Epic 1 + 2 + 3 output.
🟡 Minor Concern - Story 4.5 scope expansion: Story 4.5 AC adds: "le lien peut avoir une durée de validité configurable: 7 jours, 30 jours (défaut), ou illimitée." FR36 only says "lien partageable en lecture seule" - no mention of configurable expiry. This is a scope addition beyond the PRD.
🟡 Minor Concern - Story 4.6 implicit dependency on Story 4.5: Story 4.6 AC: "Le lien de partage est révoqué si le contributeur effacé était le seul contributeur visible sur ce lien." This assumes a share token exists (Story 4.5). Within the same epic, this is an acceptable backward dependency - but should be implemented after Story 4.5.
Acceptance Criteria Quality - Epic 4:
| Check | Status |
|---|---|
| Story 1.1 = starter template setup | ✅ Present and correct |
| Development environment config | ✅ Story 1.1 covers .env.example |
| CI/CD pipeline setup | ⚠️ Architecture has .github/workflows/ci.yml but no story covers setting up CI/CD - minor gap for greenfield |
| Schema creation per story | ✅ Implicit (acceptable) |
| Epic | Delivers User Value | Independent | Stories Sized OK | No Forward Deps | Clear ACs |
|---|---|---|---|---|---|
| Epic 1 | ✅ (1.1/1.2 technical but justified) | ✅ | ✅ | ⚠️ 1.5 minor | ✅ |
| Epic 2 | ✅ | ✅ | ⚠️ 2.4 oversized | 🟠 2.2 → 2.6 | ✅ |
| Epic 3 | ✅ | ✅ | ✅ | 🟠 3.7 → Epic 4 | ✅ |
| Epic 4 | ✅ | ✅ | ✅ | ✅ (internal only) | ✅ |
None identified. No purely technical epics with zero user value, no epic-sized stories, no circular dependencies.
Story 2.2 ↔ Story 2.6 forward dependency - Story 2.2 ACs reference "pièces jointes optionnelles" but the implementation is in Story 2.6. Fix: Remove attachments from Story 2.2 ACs, make it an explicit prerequisite that Story 2.6 must be completed or merged with 2.2 before Sprint closure.
Story 2.4 oversized - Bundles 4 FRs including significant content creation (≥25 use cases). Fix: Split into Story 2.4a (library technical feature) and Story 2.4b (library content seed).
Story 3.7 forward dependency on Epic 4 - "réponses reçues aux questions de qualification" requires Epic 4 features. Fix: Remove that clause from Story 3.7 AC and add an enhancing story in Epic 4.
Overall Epic Quality: GOOD with addressable issues. No blockers that would prevent starting implementation, but 3 major issues should be resolved before the team begins Epic 2 and Epic 3 stories.
The project is well-prepared for implementation. The PRD is thorough, the architecture is solid, the UX spec is detailed, and the epics cover 100% of the functional requirements. No critical structural failures were found. However, three major issues in the epic stories must be resolved before implementation of Epics 2 and 3 begins, and several notable UX-to-story gaps need explicit decisions.
| Category | Total Issues | 🔴 Critical | 🟠 Major | 🟡 Minor |
|---|---|---|---|---|
| FR Coverage (vs PRD) | 0 | 0 | 0 | 0 |
| NFR Coverage (vs PRD) | 7 | 0 | 0 | 7 |
| UX Alignment | 4 | 0 | 2 | 2 |
| Epic Story Quality | 14 | 0 | 3 | 11 |
| Total | 25 | 0 | 5 | 20 |
Issue 1 - 🟠 Story 2.2 ↔ Story 2.6 forward dependency Story 2.2 ACs include "pièces jointes optionnelles" as a form field, but file upload is implemented in Story 2.6. Story 2.2 cannot be closed as complete without Story 2.6. Fix: Reorder stories (2.6 before 2.2 or merged), or remove attachment field from Story 2.2 ACs and explicitly state it is added via Story 2.6.
Issue 2 - 🟠 Story 2.4 oversized (4 FRs + significant content creation) Story 2.4 bundles the library technical feature (FR14-IA3/IA4/IA5) with seeding ≥5 use cases per sector AND per function (FR14-IA6 - minimum 25+ content items). This is too large for a single sprint story. Fix: Split into Story 2.4a (library UI + pre-fill + CDO sharing) and Story 2.4b (content seed ≥5 cases/sector + ≥5 cases/function).
Issue 3 - 🟠 Story 3.7 forward dependency on Epic 4 Story 3.7 includes "réponses reçues aux questions de qualification" in its AC, which depends on the qualification feature in Epic 4 (Stories 4.1/4.2). Fix: Remove "réponses reçues" from Story 3.7 AC. Add a Story 4.x in Epic 4 that enhances the activity summary to include qualification responses.
Issue 4 - 🟠 UX email confirmation to contributor not in any story The UX spec's J2 flow includes an email to the contributor after submission (with CTA "Soumettre une autre idée"). This is not an FR in the PRD and not in any story. Without it, the contributor's feedback loop is incomplete. Fix: Add AC to Story 2.7 (or create Story 2.7b): "And the contributor receives a confirmation email with a CTA to submit another idea."
Issue 5 - 🟠 UX card grid view (Vue Cartes) has no story The UX spec defines a third backlog view (card grid / direction 2) alongside list and kanban. The PRD only defines FR22 (list) and FR23 (kanban). No story covers this view. Fix: Explicitly decide: (a) add to Story 3.2 as a third toggle option, OR (b) defer to post-MVP with a note in the epics document.
Fix the 3 story dependency issues in epics.md (Issues 1, 2, 3 above) - these are structural: update Story 2.2 ACs, split Story 2.4, and split Story 3.7. These can be done quickly in the epics document before the first sprint.
Decide on the email confirmation to contributor and card grid view (Issues 4, 5) - these require a PRD/scope decision. If confirmed in-scope, update the PRD FRs, update the relevant stories, and confirm architecture support. If out-of-scope for MVP, add a note in epics.md deferring to post-MVP.
Add explicit CI/CD story or developer task - Story 1.0 "Setup CI pipeline (GitHub Actions)" is missing for the greenfield project. Add as a developer task alongside Story 1.1.
Reinforce NFR coverage in story ACs (5 NFRs with no story coverage) - prioritize:
Clarify minor AC gaps - Update Story 2.5 (malformed email error case), Story 3.2 (empty filter state), Story 4.1 (qualification question limit), Story 4.5 (confirm or remove configurable expiry).
createWorkspaceProcedure and the LLM isolation rule without exception.AIBadge everywhere) are not just polish - they are the core product differentiation. The AIBadge, DepartmentPicker, ScoreSlider, and EmptyState components are critical path items.Assessment date: 2026-02-27 Assessor: AI Product Manager / Scrum Master (BMAD Check Implementation Readiness workflow) Project: agentMarketing - AImpact Hub
This assessment identified 25 issues across 4 categories: 0 critical, 5 major, 20 minor. The 5 major issues are all resolvable in 1–2 hours of epics document updates before the first implementation sprint begins. The project has strong documentation quality across all four artifacts (PRD, Architecture, UX, Epics) and is fundamentally ready for a greenfield implementation start.
Proceed to implementation after resolving the 5 major issues. Epic 1 can begin immediately as-is.
The following fixes were applied to epics.md following the assessment:
Status: All 5 major issues resolved. Implementation can proceed.