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>
2.4 KiB
2.4 KiB
name, description
| name | description |
|---|---|
| evolution | Add features to existing products through targeted changes |
[E] Evolution — Add Features to Existing Product
Goal: Incrementally add features to an existing product with minimal disruption.
When to use: Existing product needs new functionality. Changes should be targeted, not a complete rewrite.
CORE PRINCIPLES
- Backward compatible — Existing functionality must keep working. Every change is verified against what already exists.
- Feature flags if needed — When a change is risky or requires staged rollout, use feature flags to decouple deployment from activation.
- Incremental delivery — Ship in small, verifiable increments. Each commit should leave the system in a working state.
INITIALIZATION
Design Log
Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.
Essential Guides
- Execution Principles — Document-first, plan-then-execute
- Session Protocol — Read dialog, verify plan, present status
- Inline Testing Guide — Baseline capture before modifying existing features
STEPS
Execute steps in ./steps-e/:
| Step | File | Purpose |
|---|---|---|
| 01 | step-01-scope-change.md | Define what changes vs what stays |
| 02 | step-02-analyze-impact.md | Analyze impact on existing code |
| 03 | step-03-plan-implementation.md | Plan incremental implementation |
| 04 | step-04-implement.md | Implement changes |
| 05 | step-05-verify-and-document.md | Verify, regression check, document |
Flow: 01 → 02 → 03 → 04 → 05
Critical Rules
- ALWAYS map what is new vs what is modified vs what is untouched before coding
- ALWAYS capture baseline state of existing features before modifying them
- ALWAYS verify backward compatibility at each commit
- ALWAYS plan incremental commits — never one giant change
- NEVER break existing functionality to add new functionality
- NEVER skip impact analysis — surprises in production are expensive
AFTER COMPLETION
- Append a progress entry to
{output_folder}/_progress/00-design-log.mdunder## Progress:### [date] — Evolution: [what was evolved/added] - Suggest acceptance testing (Phase 5 [T]) to validate the changes