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>
108 lines
4.0 KiB
Markdown
108 lines
4.0 KiB
Markdown
---
|
|
name: 'step-02b-explore-solution'
|
|
description: 'Capture solution idea and explore the underlying realization when user starts with a solution'
|
|
|
|
# File References
|
|
nextStepFile: './step-02c-explore-why-it-matters.md'
|
|
workflowFile: '../workflow.md'
|
|
---
|
|
|
|
# Step 7: Explore Solution (If Starting with Solution)
|
|
|
|
## STEP GOAL:
|
|
|
|
Capture the user's solution idea and then explore the underlying realization that led to it.
|
|
|
|
## 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 the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
|
|
- ✅ 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 alignment and stakeholder management expertise, user brings their project knowledge
|
|
- ✅ Maintain a supportive and clarifying tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus only on capturing the solution idea and connecting it to a realization
|
|
- 🚫 FORBIDDEN to evaluate or critique the solution prematurely
|
|
- 💬 Approach: Capture first, then explore the underlying why
|
|
- 📋 Bridge from solution back to realization, then forward to why it matters
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Capture the solution idea and connect it to a realization
|
|
- 💾 Store both the solution idea and underlying realization
|
|
- 📖 This step is for users who start with a solution rather than a realization
|
|
- 🚫 Do not skip exploring the underlying realization
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: User's situation, starting point choice (solution-first)
|
|
- Focus: Solution idea and underlying realization
|
|
- Limits: Do not explore other sections yet
|
|
- Dependencies: step-01e must be completed with solution-first routing
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Capture the Solution
|
|
|
|
If user starts with a solution idea:
|
|
|
|
1. **Capture the solution**: "Tell me about your solution idea..."
|
|
|
|
### 2. Explore the Underlying Realization
|
|
|
|
2. **Then explore the underlying realization**: "What realization does this solution address? What have you observed that led to this solution?"
|
|
|
|
### 3. Connect to Why It Matters
|
|
|
|
3. **Then explore why it matters**: "Why does this matter? Who are we helping?"
|
|
|
|
### 4. Explore Other Approaches
|
|
|
|
4. **Then explore other approaches**: "What other ways could we approach this?"
|
|
|
|
### 5. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to step-02c-explore-why-it-matters"
|
|
|
|
#### Menu Handling Logic:
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF M: Return to {workflowFile}
|
|
- 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
|
|
- ONLY proceed to next step when user selects 'C'
|
|
- User can chat or ask questions - always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN the solution idea and underlying realization are captured will you then load and read fully `{nextStepFile}` to execute and begin the next step.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
- Solution idea is clearly captured
|
|
- Underlying realization is identified and connected to the solution
|
|
- User sees the relationship between their solution and the problem it addresses
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
- Skipping the exploration of the underlying realization
|
|
- Critiquing or dismissing the user's solution idea
|
|
- Moving forward without connecting solution to realization
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|