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>
98 lines
3.8 KiB
Markdown
98 lines
3.8 KiB
Markdown
---
|
|
name: 'step-08-success-criteria'
|
|
description: 'Help user define measurable success criteria'
|
|
|
|
# File References
|
|
nextStepFile: './step-09-competitive-landscape.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow.md'
|
|
---
|
|
|
|
# Step 8: Define Success Criteria
|
|
|
|
## STEP GOAL:
|
|
Help the user explore and define what success looks like through conversational questioning, then synthesize into clear, measurable SMART criteria.
|
|
|
|
## 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, a strategic interviewer helping user think through success from multiple angles
|
|
- 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 thinking and facilitation skills, user brings domain expertise and product vision
|
|
- Maintain professional, collaborative tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
- Focus: Success from multiple angles: user behavior, business outcomes, experience quality, timeline
|
|
- FORBIDDEN: Do not say this needs to be SMART - ask the questions that naturally make it SMART
|
|
- Approach: Explore success dimensions naturally, help translate outcomes to metrics, prioritize
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
- Primary goal: Measurable success criteria with primary/secondary metrics and timeline
|
|
- Save/document outputs appropriately
|
|
- Avoid generating content without user input
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
- Available context: Vision, positioning, Trigger Map, business model, target users, product concept
|
|
- Focus: Measurable success criteria with primary/secondary metrics and timeline
|
|
- Limits: Not business model changes, not competitive analysis
|
|
- Dependencies: Steps 1-7a completed
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Open the Conversation
|
|
Ask about what changes when this launches and is working well.
|
|
|
|
### 2. Explore Success from Multiple Angles
|
|
A) User Behavior Success B) Business Outcome Success C) Experience Quality D) Timeline
|
|
|
|
### 3. Help Make Criteria SMART
|
|
Ask questions that naturally make criteria Specific, Measurable, Achievable, Relevant, Time-bound.
|
|
|
|
### 4. Prioritize if Multiple
|
|
Ask which is most important.
|
|
|
|
### 5. Confirm and Document
|
|
Reflect back. Get confirmation. Document in product brief.
|
|
|
|
### 6. Design Log Update
|
|
Mandatory: Append to dialog/decisions.md. Mark Step 8 complete.
|
|
|
|
### N. Present MENU OPTIONS
|
|
Display: "**Select an Option:** [C] Continue to next step"
|
|
|
|
#### 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]
|
|
|
|
#### 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 step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
|
|
|
|
---
|
|
|
|
## SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### SUCCESS:
|
|
- Success explored through multiple angles
|
|
- SMART criteria synthesized from conversation
|
|
- Primary and secondary metrics identified
|
|
- User confirmed
|
|
|
|
### FAILURE:
|
|
- Simply asked What are your success criteria without exploration
|
|
- Generated criteria without user input
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|