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.0 KiB
2.0 KiB
name, description, borrows_from
| name | description | borrows_from |
|---|---|---|
| deploy | Create PR and deliver the improvement to the team | Phase 4 [H] (design delivery) |
Deploy
Goal: Package the tested improvement as a PR and deliver it to the development team.
INITIALIZATION
Design Log
Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.
Steps
Step 1: Pre-Deploy Checklist
Verify everything is ready:
- All acceptance criteria pass (from [T] test report)
- Branch is clean (no uncommitted changes)
- Commits are logical and well-described
- No unrelated changes included
- Documentation updated (if applicable)
Step 2: Create Pull Request
Create a PR from the evolution branch:
gh pr create --title "[Improvement]: [Brief description]" --body "..."
PR body includes:
- What changed — Summary of the improvement
- Why — Link to scenario and analysis
- How to test — Steps from the test report
- Screenshots — Before/after if visual change
- Acceptance criteria — Checklist from spec
Step 3: Package Delivery Context
Create a delivery summary at {output_folder}/evolution/deliveries/:
# Delivery: [Scenario Name]
## PR
[Link to PR]
## Artifacts
- Analysis: [link]
- Scenario: [link]
- Specification: [link]
- Test Report: [link]
## Change Summary
[What was changed and why]
## Impact
[Expected improvement based on success criteria]
## Monitoring
[What to watch after deployment — metrics, error rates, user feedback]
Step 4: Notify Team
If the project uses design log tracking or team notifications:
- Create completion notification
- Reference all artifacts (analysis → scenario → spec → test → PR)
- Include any monitoring instructions
Step 5: Plan Next Cycle
After deployment:
- Archive this improvement cycle
- Review remaining improvement targets from [A] analysis
- Suggest next target or new analysis round
AFTER COMPLETION
- Update design log with completed improvement
- Return to Phase 8 Activity Menu for next cycle