julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
66 lines
2.5 KiB
Markdown
66 lines
2.5 KiB
Markdown
# Product Brief: SAR
|
|
|
|
> The strategic foundation — why this product exists, who it serves, and what success looks like.
|
|
|
|
**Created:** 2026-05-26
|
|
**Phase:** 1 — Product Brief
|
|
**Agent:** Saga (Analyst)
|
|
|
|
---
|
|
|
|
## What Belongs Here
|
|
|
|
The Product Brief answers five strategic questions:
|
|
|
|
1. **Why** does this product exist? (Vision & business goals)
|
|
2. **Who** is it for? (Target users and their context)
|
|
3. **What** does it need to do? (Core capabilities)
|
|
4. **How** will we know it works? (Success metrics)
|
|
5. **What** are the constraints? (Platform requirements, tech stack)
|
|
|
|
Everything downstream — trigger maps, scenarios, page specs, design system — traces back to decisions made here. This is the North Star.
|
|
|
|
**Learn more:**
|
|
- WDS Course Module 04: Product Brief — Your Strategic Foundation
|
|
- WDS Course Module 05: Platform Requirements
|
|
|
|
---
|
|
|
|
## For Agents
|
|
|
|
**Workflow:** `skill:wds-1-project-brief`
|
|
**Agent trigger:** `PB` (Saga)
|
|
**Templates:** `./resources/wds-1-project-brief/templates/`
|
|
|
|
**Before writing anything in this folder:**
|
|
1. Load the workflow and follow its steps
|
|
2. Use Dialog mode for discovery — ask questions, don't assume
|
|
3. Read existing materials if the user has them (check `wds-project-outline.yaml`)
|
|
|
|
**Existing materials available** (see `_progress/wds-project-outline.yaml`):
|
|
- `brand.md` — identidade visual JCS (paleta, tipografia, layout)
|
|
- `STACK.md` — stack canônica JCS v2.2 (Node 24, Nest 11, Prisma 7, React 19.2, AntD 6.4, Proxmox)
|
|
- `CODING-RULES.md` — invariantes + pegadinhas 🔥 (PGD-SEC, PGD-DB, etc.)
|
|
- `frontend/img/SAR_logo_fundo_transparente.png` + `SAR_icone_fundo_transparente.png`
|
|
|
|
**File naming:** Number all documents with a two-digit prefix: `01-product-brief.md`, `02-content-language.md`, etc. Platform Requirements is always last — it summarizes technical decisions that emerge from the strategic documents above. Update the Documents table below as each file is created.
|
|
|
|
**Harm:** Producing a brief from assumptions instead of conversation. A brief that doesn't reflect the user's actual goals forces every later phase to build on a wrong foundation.
|
|
|
|
**Help:** Asking the right questions, listening deeply, and documenting what the user actually said. A good brief makes every later decision easier.
|
|
|
|
---
|
|
|
|
## Documents
|
|
|
|
_This section will be updated as documents are created during Phase 1._
|
|
|
|
| # | Document | Status |
|
|
|---|----------|--------|
|
|
| 01 | Product Brief | Not started |
|
|
| 02 | Platform Requirements | Not started |
|
|
|
|
---
|
|
|
|
_Created using Whiteport Design Studio (WDS) methodology_
|