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>
120 lines
4.5 KiB
Markdown
120 lines
4.5 KiB
Markdown
---
|
|
name: 'step-02h-explore-value-we-create'
|
|
description: 'Help user articulate what happens if we DO build this - ambition, success metrics, and outcomes'
|
|
|
|
# File References
|
|
nextStepFile: './step-02i-explore-cost-of-inaction.md'
|
|
workflowFile: '../workflow.md'
|
|
|
|
# Data References
|
|
sectionRoutingFile: '../data/02-explore-sections-routing.md'
|
|
---
|
|
|
|
# Step 13: Explore The Value We'll Create
|
|
|
|
## STEP GOAL:
|
|
|
|
Help the user articulate what happens if we DO build this - the ambition, success metrics, expected outcomes, and how to measure success.
|
|
|
|
## 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 exploring the value that will be created
|
|
- 🚫 FORBIDDEN to generate value statements without user input
|
|
- 💬 Approach: Frame as positive assumption with success metrics
|
|
- 📋 Keep it brief - key benefits, outcomes, and success metrics
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Help user articulate value, ambition, and success metrics
|
|
- 💾 Capture value proposition for the alignment document
|
|
- 📖 Reference `{sectionRoutingFile}` (Section 7: The Value We'll Create)
|
|
- 🚫 Do not fabricate benefits or metrics
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: All previous exploration sections
|
|
- Focus: The Value We'll Create section of the alignment document
|
|
- Limits: Key benefits and metrics, not exhaustive analysis
|
|
- Dependencies: step-02g must be completed
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Explore the Value We'll Create
|
|
|
|
Explore the value we'll create.
|
|
|
|
**Reference**: `{sectionRoutingFile}` (Section 7: The Value We'll Create)
|
|
|
|
**Questions to explore**:
|
|
- "What's our ambition? What are we striving to accomplish?"
|
|
- "What happens if we DO build this?"
|
|
- "What benefits would we see?"
|
|
- "What outcomes are we expecting?"
|
|
- "How will we measure success?"
|
|
- "What metrics will tell us we're succeeding?"
|
|
- "What's the value we'd create?"
|
|
|
|
### 2. Frame as Positive Assumption with Success Metrics
|
|
|
|
**Help them articulate**:
|
|
- **Our Ambition**: What we're confidently striving to accomplish (enthusiastic, positive)
|
|
- **Success Metrics**: How we'll measure success (specific, measurable)
|
|
- **What Success Looks Like**: Clear outcomes (tangible results)
|
|
- **Monitoring Approach**: How we'll track these metrics (brief)
|
|
|
|
**Keep it brief** - Key benefits, outcomes, and success metrics
|
|
|
|
**Help them think**: Positive assumption ("We're confident this will work") + clear success metrics ("Here's how we'll measure it") = enthusiastic and scientific
|
|
|
|
### 3. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to step-02i-explore-cost-of-inaction"
|
|
|
|
#### 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 user has articulated the value, ambition, and success metrics will you then load and read fully `{nextStepFile}` to execute and begin the next step.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
- Clear ambition and value proposition captured
|
|
- Success metrics are specific and measurable
|
|
- Positive and confident framing
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
- Generating value statements without user input
|
|
- Skipping success metrics
|
|
- Not framing as positive assumption
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|