- 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>
181 lines
5.6 KiB
Markdown
181 lines
5.6 KiB
Markdown
---
|
|
name: 'step-02-business-goals'
|
|
description: 'Workshop 1: Define business vision and SMART objectives'
|
|
|
|
# File References
|
|
nextStepFile: './step-03-target-groups.md'
|
|
activityWorkflowFile: '../workflow.md'
|
|
---
|
|
|
|
# Step 8: Workshop 1 - Business Goals
|
|
|
|
## STEP GOAL:
|
|
|
|
Facilitate Workshop 1 to define the user's business vision and transform it into SMART strategic objectives that will guide all design decisions.
|
|
|
|
## 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 - facilitating strategic clarity
|
|
- ✅ 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 capturing vision and creating SMART objectives
|
|
- 🚫 FORBIDDEN to define vision or objectives without user input
|
|
- 💬 Approach: Start with the dream, then make it measurable
|
|
- 📋 Aim for 3-5 clear objectives
|
|
- 📋 Help transform vague metrics into SMART format
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Facilitate vision capture through aspirational questions
|
|
- 💾 Store vision_statement and objectives
|
|
- 📖 Help refine each objective to SMART format
|
|
- 🚫 Do not proceed until objectives are confirmed
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Product Brief, configuration
|
|
- Focus: Vision statement and SMART objectives
|
|
- Limits: User must provide the vision - do not invent it
|
|
- Dependencies: Requires Phase 1 Product Brief
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Introduce Workshop
|
|
|
|
Output:
|
|
"**Workshop 1: Business Goals**
|
|
|
|
We'll define what success looks like at two levels:
|
|
|
|
- **Vision** - The inspiring, aspirational goal (not easily quantified)
|
|
- **Objectives** - SMART metrics that indicate progress
|
|
|
|
Let's start with the dream, then make it measurable."
|
|
|
|
### 2. Capture the Vision
|
|
|
|
Ask:
|
|
"**Where do you want to be?**
|
|
|
|
Think big. If everything goes perfectly, what position do you want to hold?
|
|
|
|
Examples:
|
|
- 'Be the most trusted platform for dog owners in Sweden'
|
|
- 'The go-to tool for indie designers'
|
|
- 'Make project management actually enjoyable'"
|
|
|
|
Listen for aspirational, motivating language.
|
|
Help refine into a clear, inspiring vision statement.
|
|
|
|
Output: "**Your Vision:** {{vision_statement}}"
|
|
|
|
Store vision_statement.
|
|
|
|
### 3. Break Down into Objectives
|
|
|
|
Output: "Now let's make this measurable. What would indicate you're achieving that vision?"
|
|
|
|
Ask:
|
|
"**How would you measure progress toward this vision?**
|
|
|
|
Think about:
|
|
- User metrics (adoption, engagement, retention)
|
|
- Business metrics (revenue, growth, market share)
|
|
- Quality metrics (satisfaction, referrals, reviews)
|
|
|
|
What numbers would make you confident you're on track?"
|
|
|
|
For each metric mentioned, help make it SMART:
|
|
- **S**pecific - What exactly?
|
|
- **M**easurable - What number?
|
|
- **A**chievable - Is this realistic?
|
|
- **R**elevant - Does this connect to the vision?
|
|
- **T**ime-bound - By when?
|
|
|
|
Aim for 3-5 clear objectives.
|
|
|
|
### 4. Refine Objectives
|
|
|
|
Output: "Let me help sharpen these into SMART objectives."
|
|
|
|
Walk through each objective with example transformation:
|
|
- Vague: "Get influential users"
|
|
- SMART: "Onboard 10 verified dog trainers with 1000+ followers by Q4 2026"
|
|
|
|
Present each refined objective for confirmation.
|
|
|
|
Ask for any adjustments.
|
|
|
|
Store objectives.
|
|
|
|
### 5. Present Workshop Summary
|
|
|
|
Output:
|
|
"**Workshop 1 Complete!**
|
|
|
|
**Vision:**
|
|
{{vision_statement}}
|
|
|
|
**Objectives:**
|
|
{{#each objectives}}
|
|
{{@index + 1}}. {{this.statement}}
|
|
{{/each}}
|
|
|
|
This gives us clear targets to work toward. Next, we'll identify who can help you achieve these goals."
|
|
|
|
Store vision_statement and objectives for next workshop.
|
|
|
|
### 6. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Target Groups Workshop | [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. Vision and objectives must be confirmed before proceeding.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
- Vision statement captured from user input (not generated)
|
|
- 3-5 SMART objectives defined and confirmed
|
|
- Each objective is Specific, Measurable, Achievable, Relevant, Time-bound
|
|
- Vague metrics transformed into measurable goals
|
|
- User confirmed both vision and objectives
|
|
- Results stored for subsequent workshops
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
- Generating vision without user input
|
|
- Accepting vague, unmeasurable objectives
|
|
- Having fewer than 3 or more than 5 objectives without discussion
|
|
- Not applying SMART framework to each objective
|
|
- Proceeding without user confirmation
|
|
- Not storing results for next workshop
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|