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>
139 lines
4.8 KiB
Markdown
139 lines
4.8 KiB
Markdown
---
|
|
name: 'step-07b-generate-business-goals'
|
|
description: 'Generate the 01-Business-Goals.md document with vision, objectives, and flywheel'
|
|
|
|
# File References
|
|
nextStepFile: './step-07c-generate-primary-persona.md'
|
|
activityWorkflowFile: '../workflow.md'
|
|
|
|
# Data References
|
|
businessGoalsTemplate: '../data/business-goals-template.md'
|
|
---
|
|
|
|
# Step 18: Generate Business Goals Document
|
|
|
|
## STEP GOAL:
|
|
|
|
Create the comprehensive 01-Business-Goals.md document with vision statement, SMART objectives across priority tiers, the flywheel explanation, and success metrics alignment.
|
|
|
|
## 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 - documenting strategic foundation
|
|
- ✅ 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 creating comprehensive business goals document
|
|
- 🚫 FORBIDDEN to use "convert users" language - use "create awesome" language
|
|
- 💬 Approach: Empowering, organic growth language throughout
|
|
- 📋 Use template from {businessGoalsTemplate}
|
|
- 📋 PRIMARY GOAL clearly marked as THE ENGINE; target ~150-160 lines
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Generate document following template structure
|
|
- 💾 Save as 01-Business-Goals.md in trigger map folder
|
|
- 📖 Reference template for complete structure
|
|
- 🚫 Do not use "converting" language
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Vision, objectives, priorities from workshops
|
|
- Focus: Business goals document with flywheel
|
|
- Limits: Use empowering language, mark PRIMARY clearly as THE ENGINE
|
|
- Dependencies: Requires completed workshops and hub document
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Reference Template
|
|
|
|
See {businessGoalsTemplate} for the complete template structure.
|
|
|
|
### 2. Generate Document Sections
|
|
|
|
Include:
|
|
1. **Header** - Project name, date, status
|
|
2. **Vision Statement** - 1-2 sentence transformation goal
|
|
3. **Business Objectives** - 3 priority tiers (Primary/Secondary/Tertiary)
|
|
4. **The Flywheel** - How goals connect causally
|
|
5. **Success Metrics Alignment** - Persona to objective connections
|
|
6. **Related Documents Footer** - Links to other trigger map docs
|
|
|
|
**Language Requirements:**
|
|
- "Create awesome [users]" NOT "convert users"
|
|
- "Naturally become [champions]" NOT "make them champions"
|
|
- Empowering, organic growth language
|
|
|
|
**Priority Clarity:**
|
|
- PRIMARY GOAL clearly marked as THE ENGINE
|
|
- SECONDARY driven by primary
|
|
- TERTIARY benefits FOR members (not company revenue)
|
|
|
|
**SMART Objectives:**
|
|
- Specific, Measurable, Achievable, Relevant, Time-bound
|
|
|
|
**Flywheel Logic:**
|
|
- Shows causal relationships
|
|
- Emphasizes natural emergence
|
|
- Makes primary goal's importance clear
|
|
|
|
### 3. Save and Confirm
|
|
|
|
Store as: 01-Business-Goals.md in trigger map folder.
|
|
|
|
Output: "Business goals document created with flywheel!"
|
|
|
|
### 4. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Primary Persona Document | [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. Document must be generated and saved before proceeding. Do NOT skip ahead.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
- Document generated with all 6 sections
|
|
- Vision statement clear and inspiring
|
|
- 3 priority tiers with SMART objectives
|
|
- PRIMARY GOAL marked as THE ENGINE
|
|
- Flywheel showing causal relationships
|
|
- Empowering language throughout (no "convert" language)
|
|
- ~150-160 lines
|
|
- Document saved to correct location
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
- Missing required sections
|
|
- Using "convert users" or similar language
|
|
- PRIMARY GOAL not clearly marked
|
|
- Missing flywheel explanation
|
|
- Objectives not SMART
|
|
- Not saved to correct location
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|