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>
1.7 KiB
1.7 KiB
name, description, borrows_from
| name | description | borrows_from |
|---|---|---|
| analyze-product | Understand current product state and find improvement targets | Phase 3 (scenarios) |
Analyze Product
Goal: Understand the existing product, identify what needs improving, and prioritize targets.
INITIALIZATION
Design Log
Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.
Steps
Step 1: Load Product Context
Gather existing product information:
- Read project configuration and any existing WDS artifacts
- If the product has a live URL → analyze current state (structure, pages, flows)
- If codebase available → scan for tech stack, component patterns, design tokens
- Document what exists: pages, navigation, key user flows
Present a Product Snapshot — current state summary.
Step 2: Identify Improvement Targets
With the user, identify what needs work:
- User feedback — What are users struggling with?
- Business goals — What metrics need improvement?
- Technical debt — What's fragile or outdated?
- Visual gaps — What looks inconsistent or dated?
- Competitor gaps — What are competitors doing better?
Create a prioritized list of improvement targets.
Step 3: Select Target
From the prioritized list, pick ONE target for this improvement cycle:
Improvement targets (prioritized):
1. [Target] — [Impact] — [Effort]
2. [Target] — [Impact] — [Effort]
...
Which target should we tackle first?
Step 4: Document Analysis
Save analysis to {output_folder}/evolution/analysis/:
- Product snapshot
- Improvement targets with priorities
- Selected target with rationale
AFTER COMPLETION
- Update design log
- Suggest next action
- Return to activity menu