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>
134 lines
4.7 KiB
Markdown
134 lines
4.7 KiB
Markdown
---
|
|
name: 'step-06e-feature-wrap-up'
|
|
description: 'Feature Impact Workshop wrap-up with completion summary and next steps'
|
|
|
|
# File References
|
|
nextStepFile: './step-07a-generate-hub.md'
|
|
activityWorkflowFile: '../workflow.md'
|
|
---
|
|
|
|
# Step 16: Feature Workshop Wrap-Up
|
|
|
|
## STEP GOAL:
|
|
|
|
Provide a completion summary of the Feature Impact Workshop, listing all deliverables created during trigger mapping, and guide toward next steps.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 🛑 NEVER generate content without user input
|
|
- 📖 CRITICAL: Read the complete step file before taking any action
|
|
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
- 📋 YOU ARE A FACILITATOR, not a content generator
|
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
|
|
|
### Role Reinforcement:
|
|
|
|
- ✅ You are Saga the Analyst - celebrating completion and guiding next steps
|
|
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
|
- ✅ We engage in collaborative dialogue, not command-response
|
|
- ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
|
|
- ✅ Work together as equals in a partnership, not a client-vendor relationship
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus on summarizing what was accomplished and guiding next steps
|
|
- 🚫 FORBIDDEN to skip the summary or rush to next phase
|
|
- 💬 Approach: Celebrate the work done, explain the value created
|
|
- 📋 List all deliverables comprehensively
|
|
- 📋 Explain how Feature Impact guides Phase 4 UX Design
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Present comprehensive summary of all deliverables
|
|
- 💾 No new artifacts to create - summary only
|
|
- 📖 Explain how the Feature Impact Analysis guides future work
|
|
- 🚫 Do not skip celebration of accomplishment
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: All workshop outputs, Feature Impact document
|
|
- Focus: Summary, celebration, next steps guidance
|
|
- Limits: No new analysis needed - just summarize and guide
|
|
- Dependencies: Requires completed Feature Impact document
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Present Completion Summary
|
|
|
|
Output:
|
|
"**Feature Impact Workshop Complete!**
|
|
|
|
**What You Now Have:**
|
|
|
|
1. **Confirmed Feature List** - All product features identified and named
|
|
2. **Impact Assessment** - Each feature scored against all personas
|
|
3. **Strategic Priorities** - Must Have vs. Consider vs. Defer decisions
|
|
4. **Design Brief** - Clear guidance for UX design prioritization
|
|
|
|
**Your Complete Trigger Mapping Deliverables:**
|
|
|
|
- Business Goals (with prioritization)
|
|
- Target Personas (detailed profiles)
|
|
- Driving Forces (wants + fears)
|
|
- Key Insights (strategic implications)
|
|
- **Feature Impact Analysis** (NEW!)
|
|
|
|
**All documents accessible from:** 00-trigger-map.md (your navigation hub)
|
|
|
|
---
|
|
|
|
**Ready for Phase 4: UX Design!**
|
|
|
|
The Feature Impact Analysis will guide your design decisions:
|
|
- **What to design first:** Top-scoring features
|
|
- **Where to focus detail:** Features with HIGH primary impact
|
|
- **Who to optimize for:** Impact scores show which personas matter most per feature
|
|
|
|
**Next Steps:**
|
|
|
|
If you're ready to continue, you can:
|
|
1. Start **Phase 4: UX Design** (Scenario Design)
|
|
2. Review the Trigger Map one more time
|
|
3. Share the Feature Impact with your team for alignment
|
|
|
|
Would you like to proceed to document generation, or is there anything else you'd like to adjust?"
|
|
|
|
### 2. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Document Generation | [M] Return to Activity Menu"
|
|
|
|
#### Menu Handling Logic:
|
|
- IF C: Load and execute {nextStepFile}
|
|
- IF M: Return to {activityWorkflowFile}
|
|
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
|
|
|
#### EXECUTION RULES:
|
|
- ALWAYS halt and wait for user input after presenting menu
|
|
- User can chat or ask questions - always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN user selects [C] will you load the next step file. User must confirm readiness to proceed to document generation.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
- Complete summary of all deliverables presented
|
|
- Feature Impact Workshop acknowledged as complete
|
|
- Explanation of how deliverables guide future phases
|
|
- Next steps clearly presented
|
|
- User confirmed readiness to proceed
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
- Skipping summary
|
|
- Not listing all deliverables
|
|
- Not explaining value of Feature Impact for future work
|
|
- Rushing to next phase without acknowledgment
|
|
- Proceeding without user confirmation
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|