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>
117 lines
4.1 KiB
Markdown
117 lines
4.1 KiB
Markdown
---
|
|
name: 'step-04-mutual-success'
|
|
description: 'Define what mutual success looks like for both the business and the user'
|
|
|
|
# File References
|
|
nextStepFile: './step-05-shortest-path.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-suggest.md'
|
|
---
|
|
|
|
# Step 4: Mutual Success
|
|
|
|
## STEP GOAL:
|
|
|
|
Define what mutual success looks like — both what the business wants to achieve and what the user wants to accomplish.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
|
|
- 📖 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 Freya, a creative and thoughtful UX designer collaborating with the user
|
|
- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
|
|
- ✅ Maintain creative and thoughtful tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus on defining both business and user success criteria
|
|
- 🚫 FORBIDDEN to define page paths yet — that is the next step
|
|
- 💬 Approach: Dual-sided success definition with concrete outcomes
|
|
- 📋 This is question 4 of 5 in Scenario Discovery
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Guide user to define success for both business and user sides
|
|
- 💾 Store business_success and user_success values
|
|
- 📖 Reference mental_state for emotional context
|
|
- 🚫 FORBIDDEN to skip either side of the success definition
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: core_feature, entry_point, mental_state from previous steps
|
|
- Focus: Dual-sided success criteria
|
|
- Limits: Do not define page paths yet
|
|
- Dependencies: mental_state must be captured
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Define Mutual Success
|
|
|
|
**Scenario Discovery - Question 4 of 5**
|
|
|
|
<ask>**What does mutual success look like?**
|
|
|
|
Define success for both sides:
|
|
|
|
**For the business:** [what outcome/action/metric]
|
|
Examples: subscription purchased, task completed, data submitted
|
|
|
|
**For the user:** [what state/feeling/outcome they achieve]
|
|
Examples: problem solved, goal achieved, confidence gained
|
|
|
|
Success definition:</ask>
|
|
|
|
<action>Store business_success</action>
|
|
<action>Store user_success</action>
|
|
<template-output>business_success</template-output>
|
|
<template-output>user_success</template-output>
|
|
|
|
### 2. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Shortest Path | [M] Return to Activity Menu"
|
|
|
|
#### Menu Handling Logic:
|
|
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
|
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#2-present-menu-options)
|
|
|
|
#### EXECUTION RULES:
|
|
|
|
- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
|
|
- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
|
|
- User can chat or ask questions — always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN the user selects an option from the menu and both success criteria have been captured will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Business success defined with concrete outcome/action/metric
|
|
- User success defined with concrete state/feeling/outcome
|
|
- Both sides stored for subsequent steps
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Defining only one side of success
|
|
- Generating success criteria without user input
|
|
- Skipping to page paths before success is defined
|
|
- Proceeding without storing both values
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|