docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,124 @@
|
||||
---
|
||||
name: 'step-01-target-group-coverage'
|
||||
description: 'Validate all target groups have complete driving forces'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-02-prioritization-integrity.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 1: Target Group Coverage Validation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify all target groups have complete driving forces (positive and negative), Product Promises/Answers, priority levels, and behavioral descriptions.
|
||||
|
||||
## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic 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 validation methodology expertise, user brings product knowledge
|
||||
- ✅ Maintain thorough and quality-focused tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on verifying completeness of target group coverage
|
||||
- 🚫 FORBIDDEN to skip any persona or approve incomplete driving forces
|
||||
- 💬 Approach: Systematic checklist verification per persona
|
||||
- 📋 Each persona must have: 3+ positive forces, 3+ negative forces, Product Promises/Answers, priority level, behavioral description
|
||||
- 📋 Generate coverage report table
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load and check all persona documents systematically
|
||||
- 💾 Store coverage report for final validation summary
|
||||
- 📖 Generate tabular report with status per persona
|
||||
- 🚫 Do not skip any check dimension
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All trigger map documents in {output_folder}/B-Trigger-Map/
|
||||
- Focus: Target group and driving forces completeness
|
||||
- Limits: Validation only - do not modify documents
|
||||
- Dependencies: Requires trigger map documents to exist
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load Trigger Map Hub
|
||||
|
||||
Read `{output_folder}/B-Trigger-Map/00-trigger-map.md` (or trigger-map.md) and extract all target groups.
|
||||
|
||||
### 2. Load Persona Documents
|
||||
|
||||
Read all persona files from `{output_folder}/B-Trigger-Map/`.
|
||||
|
||||
### 3. Verify Per Group
|
||||
|
||||
For each target group/persona:
|
||||
- Has at least 3 positive driving forces (wants)
|
||||
- Has at least 3 negative driving forces (fears)
|
||||
- Each driving force has a specific Product Promise
|
||||
- Each driving force has a specific Product Answer
|
||||
- Priority level assigned (Primary/Secondary/Tertiary)
|
||||
- Description is behavioral, not just demographic
|
||||
|
||||
### 4. Generate Report
|
||||
|
||||
```
|
||||
## Target Group Coverage Report
|
||||
|
||||
| Persona | Priority | + Forces | - Forces | Promises | Answers | Status |
|
||||
|---------|----------|----------|----------|----------|---------|--------|
|
||||
| [Name] | P1 | [N] | [N] | [N]/[N] | [N]/[N] | pass/warning/fail |
|
||||
|
||||
**Coverage:** [X]/[Total] personas complete
|
||||
**Gaps:** [list]
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Prioritization Integrity | [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. Coverage report must be generated before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- All personas checked against all dimensions
|
||||
- Coverage report generated with clear status per persona
|
||||
- Gaps identified and listed
|
||||
- No persona skipped
|
||||
- Report shows exact counts for forces, promises, answers
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Skipping personas in verification
|
||||
- Not checking all dimensions per persona
|
||||
- Not generating tabular report
|
||||
- Missing gap identification
|
||||
- Approving without complete verification
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,129 @@
|
||||
---
|
||||
name: 'step-02-prioritization-integrity'
|
||||
description: 'Validate prioritization rankings are internally consistent'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-03-persona-consistency.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 2: Prioritization Integrity Validation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify prioritization rankings match stated rationale and are internally consistent: exactly one Primary persona, reasonable tier distribution, documented rationale, and aligned focus statement.
|
||||
|
||||
## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic 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 validation methodology expertise, user brings product knowledge
|
||||
- ✅ Maintain thorough and quality-focused tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on priority tier consistency and rationale
|
||||
- 🚫 FORBIDDEN to approve without checking focus statement alignment
|
||||
- 💬 Approach: Systematic verification of priority logic
|
||||
- 📋 Check: exactly one P1, distribution, rationale, force rankings, focus statement
|
||||
- 📋 Identify duplicate or near-duplicate driving forces
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Verify priority tier logic and consistency
|
||||
- 💾 Store prioritization integrity report
|
||||
- 📖 Check driving force rankings per persona
|
||||
- 🚫 Do not skip focus statement verification
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All trigger map documents
|
||||
- Focus: Prioritization consistency and rationale
|
||||
- Limits: Validation only - flag issues, do not fix
|
||||
- Dependencies: Requires target group coverage validation completed
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Priority Tier Consistency
|
||||
|
||||
Check:
|
||||
- Exactly one Primary persona (P1)
|
||||
- Reasonable distribution across tiers (not all P1)
|
||||
- Priority rationale documented (why P1 > P2 > P3)
|
||||
- Business goals reference correct personas at correct priority
|
||||
|
||||
### 2. Driving Force Rankings
|
||||
|
||||
For each persona:
|
||||
- Driving forces have relative importance ranking
|
||||
- Top driving forces align with business goals
|
||||
- Negative forces are genuinely opposite/complementary to positives
|
||||
- No duplicate or near-duplicate forces
|
||||
|
||||
### 3. Focus Statement
|
||||
|
||||
Check:
|
||||
- Focus statement exists
|
||||
- Focus statement references P1 persona
|
||||
- Focus statement aligns with business goals
|
||||
|
||||
### 4. Generate Report
|
||||
|
||||
```
|
||||
## Prioritization Integrity Report
|
||||
|
||||
**Priority distribution:** P1: [N], P2: [N], P3: [N]
|
||||
**Focus statement present:** [Yes/No]
|
||||
**Consistency issues:** [N]
|
||||
|
||||
[List any conflicts or misalignments]
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Persona Consistency | [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. Prioritization integrity report must be generated before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- Priority tier distribution verified
|
||||
- Rationale checked for each priority decision
|
||||
- Driving force rankings verified per persona
|
||||
- Duplicate forces identified
|
||||
- Focus statement verified against P1 and business goals
|
||||
- Integrity report generated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Not checking for exactly one P1
|
||||
- Not verifying focus statement
|
||||
- Missing driving force ranking check
|
||||
- Not identifying duplicates
|
||||
- Skipping rationale verification
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,130 @@
|
||||
---
|
||||
name: 'step-03-persona-consistency'
|
||||
description: 'Validate persona documents match trigger map data and are internally consistent'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-04-feature-impact-alignment.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 3: Persona Consistency Validation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify persona documents match trigger map hub data and are internally consistent: names match, priority levels match, driving forces align, descriptions match, all sections complete, and personas are distinct.
|
||||
|
||||
## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic 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 validation methodology expertise, user brings product knowledge
|
||||
- ✅ Maintain thorough and quality-focused tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on hub-to-document alignment and cross-persona distinctness
|
||||
- 🚫 FORBIDDEN to approve if names or priority levels mismatch between hub and persona docs
|
||||
- 💬 Approach: Systematic cross-document comparison
|
||||
- 📋 Check: name match, priority match, force match, description match, section completeness, cross-persona distinctness
|
||||
- 📋 Each persona should represent a distinct user type
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Compare hub data against each persona document
|
||||
- 💾 Store persona consistency report
|
||||
- 📖 Verify all required sections present in each document
|
||||
- 🚫 Do not skip cross-persona distinctness check
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Hub document and all persona documents
|
||||
- Focus: Cross-document consistency and completeness
|
||||
- Limits: Validation only - flag mismatches, do not fix
|
||||
- Dependencies: Requires prioritization integrity validated
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Hub to Persona Document Alignment
|
||||
|
||||
For each persona:
|
||||
- Name matches between hub and persona document
|
||||
- Priority level matches between hub and persona document
|
||||
- Driving forces in persona doc match those in hub
|
||||
- Description in persona doc matches hub summary
|
||||
|
||||
### 2. Persona Document Completeness
|
||||
|
||||
Each persona document should have all required sections:
|
||||
- Name and role description
|
||||
- Behavioral profile (not just demographics)
|
||||
- Goals and motivations
|
||||
- Positive driving forces with Product Promises/Answers
|
||||
- Negative driving forces with Product Promises/Answers
|
||||
- Priority tier and rationale
|
||||
|
||||
### 3. Cross-Persona Distinctness
|
||||
|
||||
- Each persona represents a distinct user type
|
||||
- No significant overlap in driving forces between personas
|
||||
- Each persona has unique behavioral patterns
|
||||
|
||||
### 4. Generate Report
|
||||
|
||||
```
|
||||
## Persona Consistency Report
|
||||
|
||||
| Persona | Hub Match | Complete | Distinct | Status |
|
||||
|---------|-----------|----------|----------|--------|
|
||||
| [Name] | pass/fail | [X]/[Total] sections | pass/warning | pass/warning/fail |
|
||||
|
||||
**Consistency issues:** [list or "None"]
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Feature Impact Alignment | [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. Persona consistency report must be generated before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- All personas compared against hub data
|
||||
- Name and priority mismatches identified
|
||||
- Section completeness verified for each document
|
||||
- Cross-persona distinctness checked
|
||||
- Overlap in driving forces flagged
|
||||
- Consistency report generated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Not comparing against hub data
|
||||
- Missing section completeness check
|
||||
- Not checking cross-persona distinctness
|
||||
- Skipping driving force comparison
|
||||
- Not generating report
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,129 @@
|
||||
---
|
||||
name: 'step-04-feature-impact-alignment'
|
||||
description: 'Validate feature impact scores reference actual priorities'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-05-cross-document-coherence.md'
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 4: Feature Impact Alignment Validation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify feature impact scores reference actual persona priorities and business goals (if feature impact analysis was run). If not run, note as "Feature Impact not run" and proceed.
|
||||
|
||||
## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic 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 validation methodology expertise, user brings product knowledge
|
||||
- ✅ Maintain thorough and quality-focused tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on feature-persona alignment and priority tier consistency
|
||||
- 🚫 FORBIDDEN to skip this step even if Feature Impact was not run (note and proceed)
|
||||
- 💬 Approach: Systematic score verification against persona priorities
|
||||
- 📋 Check: scoring consistency, P1 alignment, business goal traceability
|
||||
- 📋 No P1-critical feature should be classified as "Defer"
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Check if feature impact analysis exists, then validate if present
|
||||
- 💾 Store feature impact alignment report
|
||||
- 📖 Verify scoring against persona priorities
|
||||
- 🚫 Do not skip - note status and proceed if not run
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Feature impact document (if exists), persona priorities
|
||||
- Focus: Feature-persona scoring alignment
|
||||
- Limits: If no feature impact, note and proceed
|
||||
- Dependencies: Requires persona consistency validated
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Check Prerequisite
|
||||
|
||||
Check if `{output_folder}/B-Trigger-Map/feature-impact-analysis.md` (or 06-Feature-Impact.md) exists. If not, note as "Feature Impact not run" and skip to report.
|
||||
|
||||
### 2. Feature-Persona Alignment (if exists)
|
||||
|
||||
- All features scored against all personas
|
||||
- Scoring uses consistent scale
|
||||
- High-priority personas have higher weight in scoring
|
||||
- Must Have features serve P1 persona
|
||||
|
||||
### 3. Priority Tier Consistency (if exists)
|
||||
|
||||
- "Must Have" features align with P1 needs
|
||||
- "Consider" features serve P2/P3 or secondary P1 needs
|
||||
- "Defer" features are genuinely lower priority
|
||||
- No P1-critical feature classified as "Defer"
|
||||
|
||||
### 4. Business Goal Traceability (if exists)
|
||||
|
||||
- Each feature traces to at least one business goal
|
||||
- High-impact features serve high-priority goals
|
||||
|
||||
### 5. Generate Report
|
||||
|
||||
```
|
||||
## Feature Impact Alignment Report
|
||||
|
||||
**Feature Impact status:** [Present / Not run]
|
||||
**Features scored:** [N]
|
||||
**Alignment issues:** [N]
|
||||
|
||||
[List any misalignments between feature priority and persona/goal priority]
|
||||
```
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [C] Continue to Cross-Document Coherence | [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. Feature impact alignment report must be generated (even if "not run") before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- Feature impact existence checked
|
||||
- If present: all scoring dimensions verified
|
||||
- If not present: clearly noted as "Not run"
|
||||
- P1-critical features not classified as Defer
|
||||
- Business goal traceability checked
|
||||
- Alignment report generated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Not checking if feature impact exists
|
||||
- Skipping scoring verification when present
|
||||
- P1-critical feature allowed as "Defer"
|
||||
- Missing business goal traceability check
|
||||
- Not generating report
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,156 @@
|
||||
---
|
||||
name: 'step-05-cross-document-coherence'
|
||||
description: 'Validate all trigger map documents are coherent as a set'
|
||||
|
||||
# File References
|
||||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Step 5: Cross-Document Coherence Validation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify all trigger map documents are coherent as a set - hub, personas, key insights, and feature impact tell a consistent story with matching terminology, coherent narrative, working cross-references, and accurate Mermaid diagram. Compile final validation report.
|
||||
|
||||
## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic 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 validation methodology expertise, user brings product knowledge
|
||||
- ✅ Maintain thorough and quality-focused tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on cross-document coherence and final validation summary
|
||||
- 🚫 FORBIDDEN to approve if persona names differ between documents
|
||||
- 💬 Approach: Systematic cross-document comparison and final report compilation
|
||||
- 📋 Check: terminology, narrative coherence, cross-references, Mermaid diagram accuracy
|
||||
- 📋 Compile results from ALL 5 validation steps into final report
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Verify coherence across all documents as a set
|
||||
- 💾 Save final validation report to {output_folder}/B-Trigger-Map/validation-report.md
|
||||
- 📖 Compile all 5 validation step results
|
||||
- 🚫 Do not skip Mermaid diagram verification
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All trigger map documents and all previous validation results
|
||||
- Focus: Cross-document coherence and final validation summary
|
||||
- Limits: This is the LAST validation step - must produce comprehensive report
|
||||
- Dependencies: Requires all previous validation steps completed
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Terminology Consistency
|
||||
|
||||
- Persona names identical across all documents
|
||||
- Business goal names identical across all documents
|
||||
- Priority emojis consistent (same emoji = same meaning)
|
||||
- Driving force language consistent (same force = same wording)
|
||||
|
||||
### 2. Narrative Coherence
|
||||
|
||||
- Hub document accurately summarizes persona docs
|
||||
- Key insights derive from actual trigger map data (not invented)
|
||||
- Flywheel logic makes causal sense (P1 -> P2 -> P3 chain)
|
||||
- Design implications flow from insights (not generic advice)
|
||||
|
||||
### 3. Cross-References
|
||||
|
||||
- All documents link back to hub (00-trigger-map.md)
|
||||
- Hub links to all sub-documents
|
||||
- Navigation is bidirectional
|
||||
- No broken links
|
||||
|
||||
### 4. Mermaid Diagram
|
||||
|
||||
- Diagram reflects actual data (not a rough sketch)
|
||||
- All personas present in diagram
|
||||
- All business goals present in diagram
|
||||
- Connections match driving force assignments
|
||||
- Renders correctly (no syntax errors)
|
||||
|
||||
### 5. Compile Final Validation Report
|
||||
|
||||
Compile results from all 5 validation steps:
|
||||
|
||||
```
|
||||
## Phase 2 Validation Report
|
||||
|
||||
**Project:** {project_name}
|
||||
**Date:** [date]
|
||||
**Documents validated:** [N]
|
||||
|
||||
### Results Summary
|
||||
| Check | Status | Issues |
|
||||
|-------|--------|--------|
|
||||
| Target Group Coverage | pass/warning/fail | [summary] |
|
||||
| Prioritization Integrity | pass/warning/fail | [summary] |
|
||||
| Persona Consistency | pass/warning/fail | [summary] |
|
||||
| Feature Impact Alignment | pass/warning/fail | [summary] |
|
||||
| Cross-Document Coherence | pass/warning/fail | [summary] |
|
||||
|
||||
### Critical Issues (must fix)
|
||||
[list or "None"]
|
||||
|
||||
### Warnings (should fix)
|
||||
[list or "None"]
|
||||
|
||||
### Recommendations
|
||||
[list or "All clear"]
|
||||
```
|
||||
|
||||
Save report to `{output_folder}/B-Trigger-Map/validation-report.md`
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- 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
|
||||
|
||||
This is the LAST step in the validation workflow. ONLY the [M] Return option is available. Validation report must be saved before completing.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
- Terminology consistency verified across all documents
|
||||
- Narrative coherence checked
|
||||
- Cross-references verified (bidirectional)
|
||||
- Mermaid diagram verified against actual data
|
||||
- Final validation report compiled from all 5 steps
|
||||
- Report saved to correct location
|
||||
- Critical issues, warnings, and recommendations clearly listed
|
||||
- Only [M] Return option available (last step)
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Not checking terminology across documents
|
||||
- Not verifying Mermaid diagram accuracy
|
||||
- Not compiling results from all 5 steps
|
||||
- Not saving validation report
|
||||
- Missing critical issues in report
|
||||
- Offering [C] Continue when there is no next step
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user