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,150 @@
|
||||
---
|
||||
name: 'step-00-define-purpose'
|
||||
description: 'Define the measurable job and purpose for content before generation begins'
|
||||
nextStepFile: './step-01-load-trigger-map-context.md'
|
||||
---
|
||||
|
||||
# Step 0: Define Content Purpose
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Define a clear, testable purpose statement for the content to be created — answering what it must accomplish, for whom, and how success is measured — so that all subsequent strategic steps have a focused target.
|
||||
|
||||
## 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 strategic content analyst guiding purpose definition
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring strategic content methodology, user brings their domain knowledge and context
|
||||
- ✅ Maintain a focused, outcome-oriented tone throughout
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on defining the content's measurable job
|
||||
- 🚫 FORBIDDEN to generate any actual content text in this step
|
||||
- 💬 Push for specific, testable purpose statements — reject vague goals
|
||||
- 📋 Ensure model priority emphasis is discussed before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document purpose definition as structured output
|
||||
- 📖 Validate all five areas (context, job, audience, criteria, model priorities) before proceeding
|
||||
- 🚫 FORBIDDEN to proceed without a specific, outcome-focused purpose statement
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Project configuration, page specifications, design system
|
||||
- Focus: What job this content must do and for whom
|
||||
- Limits: Do not create content — only define its purpose
|
||||
- Dependencies: None — this is the first step in the content creation workflow
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Establish Content Context
|
||||
|
||||
Ask the user: **"What content are we creating?"**
|
||||
|
||||
Examples: Landing page hero section, Product comparison table, Error message for invalid email, CTA button on pricing page, About page mission statement.
|
||||
|
||||
### 2. Define the Job To Do
|
||||
|
||||
Ask: **"What must this content accomplish?"**
|
||||
|
||||
Guide toward outcome-focused statements, not descriptions:
|
||||
|
||||
**Good:** "Convince Problem Aware users that shelf life matters" / "Enable confident product selection between us and competitors" / "Remove final purchase barrier with risk reversal"
|
||||
|
||||
**Bad:** "Describe the product" / "Explain benefits" / "Make it sound good"
|
||||
|
||||
### 3. Identify Target Audience and State
|
||||
|
||||
Ask: **"Who will read this? What state are they in?"**
|
||||
|
||||
Be specific: persona type, awareness level, emotional/mental state when they encounter this content.
|
||||
|
||||
### 4. Establish Success Criteria
|
||||
|
||||
Ask: **"How will we know this content succeeded?"**
|
||||
|
||||
Define measurable or observable outcomes: "User recognizes themselves and continues reading" / "User can choose the right tier in < 30 seconds" / "User clicks CTA feeling confident, not anxious"
|
||||
|
||||
### 5. Discuss Model Priority Emphasis
|
||||
|
||||
Ask: **"Which strategic models matter most for THIS job?"**
|
||||
|
||||
Present the Model Priority Matrix from the Content Purpose Guide. Different content types emphasize different models (Customer Awareness, Golden Circle, Badass Users, Trigger Map, Action Mapping). Discuss and assign star ratings per model.
|
||||
|
||||
### 6. Document Purpose Definition
|
||||
|
||||
Compile all answers into a structured purpose definition:
|
||||
|
||||
```yaml
|
||||
content_purpose:
|
||||
content_type: "[e.g., Landing page hero, Error message, CTA button]"
|
||||
purpose_statement: "[Action verb] + [specific audience/state] + [desired outcome]"
|
||||
audience:
|
||||
who: "[User persona or type]"
|
||||
state: "[Mental/emotional state, awareness level]"
|
||||
context: "[When/where they encounter this content]"
|
||||
success_criteria:
|
||||
- "[Observable outcome 1]"
|
||||
- "[Observable outcome 2]"
|
||||
model_priorities:
|
||||
primary: ["[Model 1]", "[Model 2]"]
|
||||
secondary: ["[Model 3]"]
|
||||
tertiary: ["[Model 4]"]
|
||||
review_question: "[How will we know this achieved its purpose?]"
|
||||
```
|
||||
|
||||
### 7. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save purpose definition, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the purpose definition is documented will you load {nextStepFile} to begin loading Trigger Map context.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Content type/context is clear
|
||||
- Purpose is specific and outcome-focused (not vague)
|
||||
- Audience and their state are defined
|
||||
- Success criteria are measurable or observable
|
||||
- Model priorities are selected based on purpose
|
||||
- Purpose statement is documented
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Accepting vague purpose statements like "describe the product"
|
||||
- Generating actual content text in this step
|
||||
- Skipping model priority discussion
|
||||
- Proceeding without documented success criteria
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,147 @@
|
||||
---
|
||||
name: 'step-01-load-trigger-map-context'
|
||||
description: 'Establish the strategic foundation by loading relevant Trigger Map context for content creation'
|
||||
nextStepFile: './step-02-awareness-strategy.md'
|
||||
---
|
||||
|
||||
# Step 1: Load Trigger Map Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Load the relevant Trigger Map context — WHO we are serving, WHAT motivates them, and WHERE they are in their awareness journey — so that all content decisions are anchored in strategy, not guesswork.
|
||||
|
||||
## 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 strategic content analyst loading the Trigger Map foundation
|
||||
- If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- We engage in collaborative dialogue, not command-response
|
||||
- You bring strategic methodology, user brings their project knowledge
|
||||
- Maintain a thorough, investigative tone — the context must be correct before proceeding
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- Focus ONLY on loading and validating the Trigger Map context
|
||||
- FORBIDDEN to generate content text or apply awareness strategy in this step
|
||||
- If no Trigger Map exists, flag the gap and work with whatever context is available
|
||||
- Ensure all fields are populated before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- Follow the Sequence of Instructions exactly
|
||||
- Document Trigger Map context for traceability
|
||||
- Check for Trigger Map in project documentation before asking user
|
||||
- FORBIDDEN to proceed without confirmed strategic context
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose definition from Step 0, project configuration
|
||||
- Focus: Loading and validating the correct Trigger Map context for this content
|
||||
- Limits: Do not apply the context yet — just load and confirm it
|
||||
- Dependencies: Purpose definition from Step 0
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Load the Trigger Map
|
||||
|
||||
Search project documentation:
|
||||
- Check `{output_folder}/B-Trigger-Map/00-trigger-map.md` (the hub document)
|
||||
- Check persona documents in `{output_folder}/B-Trigger-Map/`
|
||||
- If no Trigger Map folder exists, check Product Brief for business context
|
||||
|
||||
### 2. Identify the Relevant Context
|
||||
|
||||
Ask: **"Which business goal and persona does this content serve?"**
|
||||
|
||||
- Present the business goals from the Trigger Map — which one applies?
|
||||
- Present the personas — which one is the target audience for this content?
|
||||
- Present driving forces for that persona — which are most relevant?
|
||||
|
||||
### 3. Present and Confirm Context
|
||||
|
||||
Display the selected context:
|
||||
|
||||
```
|
||||
Business Goal: [selected goal from Trigger Map]
|
||||
Persona: [persona name and description]
|
||||
Driving Forces:
|
||||
- Positive: [relevant positive drivers]
|
||||
- Negative: [relevant negative drivers]
|
||||
Customer Awareness: [START level] → [END level]
|
||||
```
|
||||
|
||||
Ask: **"Is this the right strategic context for this content? Any adjustments?"**
|
||||
|
||||
### 4. Handle Missing Trigger Map
|
||||
|
||||
If no Trigger Map exists:
|
||||
- Explain that the Trigger Map (Phase 2) provides the strategic foundation for content
|
||||
- Recommend completing Phase 2 first for best results
|
||||
- If the user wants to proceed anyway, use whatever context is available from the Product Brief
|
||||
- Note the gap and flag that content may need revision after the Trigger Map is completed
|
||||
|
||||
### 5. Document Context
|
||||
|
||||
Save the confirmed context:
|
||||
|
||||
```yaml
|
||||
trigger_map_context:
|
||||
business_goal: "[goal text]"
|
||||
persona:
|
||||
name: "[persona name]"
|
||||
description: "[brief persona description]"
|
||||
driving_forces:
|
||||
positive: "[relevant positive drivers]"
|
||||
negative: "[relevant negative drivers]"
|
||||
customer_awareness:
|
||||
start: "[awareness level where user begins]"
|
||||
end: "[awareness level we want them to reach]"
|
||||
```
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save context, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the Trigger Map context is confirmed and documented will you load {nextStepFile} to begin applying the Customer Awareness Strategy.
|
||||
|
||||
---
|
||||
|
||||
## SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### SUCCESS:
|
||||
|
||||
- Trigger Map context is identified and loaded
|
||||
- All fields are populated (goal, persona, driving forces, awareness)
|
||||
- User confirms this is the correct context for this content
|
||||
- Context is documented for traceability
|
||||
|
||||
### FAILURE:
|
||||
|
||||
- Proceeding without confirmed strategic context
|
||||
- Generating content text in this step
|
||||
- Applying awareness strategy before context is loaded
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,167 @@
|
||||
---
|
||||
name: 'step-02-awareness-strategy'
|
||||
description: 'Apply Customer Awareness Cycle to determine language, information, and proof strategy'
|
||||
nextStepFile: './step-03-action-filter.md'
|
||||
---
|
||||
|
||||
# Step 2: Apply Customer Awareness Strategy
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Translate the Trigger Map's awareness positioning into a concrete content strategy — determining what language the user can understand, what information they need, what proof is required, and what emotional journey we are facilitating.
|
||||
|
||||
## 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 strategic content analyst applying the Customer Awareness Cycle
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring awareness level methodology, user brings audience insight
|
||||
- ✅ Maintain an empathetic, audience-focused tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on awareness strategy — language, information, proof, emotion
|
||||
- 🚫 FORBIDDEN to generate actual content text in this step
|
||||
- 💬 Explore each awareness dimension collaboratively with the user
|
||||
- 📋 All six areas must be addressed before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document the awareness strategy in structured format
|
||||
- 📖 Reference the 5 awareness levels (Unaware, Problem Aware, Solution Aware, Product Aware, Most Aware)
|
||||
- 🚫 FORBIDDEN to proceed without a complete awareness strategy
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose definition (Step 0), Trigger Map context (Step 1)
|
||||
- Focus: Translating awareness levels into content strategy decisions
|
||||
- Limits: Do not write content — define the strategy for it
|
||||
- Dependencies: Confirmed Trigger Map with awareness START and END levels
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Validate Starting Awareness Level
|
||||
|
||||
Present the START level from the Trigger Map and describe what it means. Confirm with user: does this match where users are when they encounter this content?
|
||||
|
||||
### 2. Clarify Target Awareness Level
|
||||
|
||||
Present the END level from the Trigger Map and describe the shift. Confirm: is this the right awareness goal for this content?
|
||||
|
||||
### 3. Determine Awareness-Appropriate Language
|
||||
|
||||
Explore together: What words will resonate vs. confuse at their starting level?
|
||||
|
||||
- Problem Aware: Speak in problem language first, product names later
|
||||
- Solution Aware: Can use solution category terminology
|
||||
- Product Aware: Specific features and comparisons matter
|
||||
|
||||
### 4. Define Information Priorities
|
||||
|
||||
What do they NEED to know at this stage?
|
||||
|
||||
- Problem Aware: Problem validation, emotional recognition, hint solutions exist
|
||||
- Solution Aware: How solutions work, what makes them good/bad
|
||||
- Product Aware: Specific features, proof, competitive comparison
|
||||
|
||||
Separate essential from overwhelming.
|
||||
|
||||
### 5. Identify Credibility Requirements
|
||||
|
||||
What proof do they need to believe us?
|
||||
|
||||
- Problem Aware: Personal stories, emotional validation
|
||||
- Solution Aware: Expert credentials, how-it-works explanations
|
||||
- Product Aware: Social proof, testimonials, data, comparisons
|
||||
|
||||
### 6. Map Emotional Journey
|
||||
|
||||
What emotional shift happens from START to END?
|
||||
|
||||
- Starting emotion: How they feel at START level
|
||||
- Ending emotion: How they should feel at END level
|
||||
- The emotional bridge we are building
|
||||
|
||||
### 7. Document Awareness Strategy
|
||||
|
||||
```yaml
|
||||
awareness_strategy:
|
||||
start_level: "[awareness level]"
|
||||
start_characteristics:
|
||||
- "[what they know]"
|
||||
- "[what they don't know]"
|
||||
- "[how they feel]"
|
||||
end_level: "[awareness level]"
|
||||
end_characteristics:
|
||||
- "[what they'll know]"
|
||||
- "[what they'll understand]"
|
||||
- "[how they'll feel]"
|
||||
language_guidelines:
|
||||
use: ["[appropriate terms]"]
|
||||
avoid: ["[confusing jargon]"]
|
||||
tone: "[conversational, authoritative, empathetic, etc.]"
|
||||
information_priorities:
|
||||
essential: ["[must include]"]
|
||||
helpful: ["[nice to include if space]"]
|
||||
avoid: ["[too advanced, confusing, or premature]"]
|
||||
credibility_required:
|
||||
type: "[personal story, expert credentials, data, social proof]"
|
||||
examples: ["[specific proof elements]"]
|
||||
emotional_journey:
|
||||
starting_emotion: "[frustrated, confused, etc.]"
|
||||
bridge: "[how we facilitate the shift]"
|
||||
ending_emotion: "[hopeful, confident, etc.]"
|
||||
```
|
||||
|
||||
### 8. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save awareness strategy, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the awareness strategy is fully documented will you load {nextStepFile} to begin defining the required action.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Start awareness level confirmed and understood
|
||||
- End awareness level confirmed and understood
|
||||
- Appropriate language identified (what words to use/avoid)
|
||||
- Information priorities clear (what to include/exclude)
|
||||
- Credibility requirements identified
|
||||
- Emotional journey mapped
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating content text in this step
|
||||
- Skipping any of the six awareness dimensions
|
||||
- Not confirming awareness levels with user
|
||||
- Proceeding without documented strategy
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,158 @@
|
||||
---
|
||||
name: 'step-03-action-filter'
|
||||
description: 'Apply Action Mapping to define the required user action and filter content for relevance'
|
||||
nextStepFile: './step-04-empowerment-frame.md'
|
||||
---
|
||||
|
||||
# Step 3: Define Required Action
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply Action Mapping (Cathy Moore) to identify the specific action the user must be able to take after reading this content, and use that to filter what information is truly necessary versus nice-to-know fluff.
|
||||
|
||||
## 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 strategic content analyst applying Action Mapping methodology
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring action-focused filtering methodology, user brings domain context
|
||||
- ✅ Maintain a sharp, purposeful tone — challenge anything that does not serve the action
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on identifying the required action and filtering information
|
||||
- 🚫 FORBIDDEN to generate content text in this step
|
||||
- 💬 Push for specific behavioral actions, not vague "understanding"
|
||||
- 📋 Challenge nice-to-know content that does not enable the action
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document the action filter in structured format
|
||||
- 📖 Work backward from action to essential information
|
||||
- 🚫 FORBIDDEN to proceed without a specific action and information filter
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness Strategy (Step 2)
|
||||
- Focus: What action must the user take, and what information enables it
|
||||
- Limits: Do not write content — filter what information to include
|
||||
- Dependencies: Trigger Map and Awareness Strategy from previous steps
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Identify the Required Action
|
||||
|
||||
Ask: **"After reading this content, what must the user be able to DO?"**
|
||||
|
||||
Push for specific behaviors, not vague understanding:
|
||||
|
||||
**Good:** "Click the signup button with confidence" / "Choose the right pricing tier" / "Complete the first onboarding step"
|
||||
|
||||
**Bad:** "Understand our features" / "Learn about our company" / "Be aware of the benefits"
|
||||
|
||||
### 2. Connect Action to Business Goal
|
||||
|
||||
Trace the logic: User does [action] → which leads to [outcome] → which drives [business goal from Trigger Map].
|
||||
|
||||
Ask: **"Does this action clearly serve the Trigger Map's business goal?"**
|
||||
|
||||
### 3. Connect Action to Driving Forces
|
||||
|
||||
From the Trigger Map driving forces: **"By taking this action, how does the user move toward their wish or away from their fear?"**
|
||||
|
||||
### 4. Determine Essential Information
|
||||
|
||||
Work backward from the action:
|
||||
- To do the action, the user must understand X
|
||||
- To understand X, they need to know Y
|
||||
- To know Y, we must tell them Z
|
||||
|
||||
Ask: **"What can we cut without preventing the action?"** Strip away everything else.
|
||||
|
||||
### 5. Identify Action Barriers
|
||||
|
||||
Ask: **"What might prevent the user from taking this action?"**
|
||||
|
||||
Common barriers: Confusion, Fear, Effort, Distrust, Irrelevance.
|
||||
|
||||
For each barrier, identify what content removes it.
|
||||
|
||||
### 6. Document Action Filter
|
||||
|
||||
```yaml
|
||||
action_filter:
|
||||
required_action:
|
||||
description: "[Specific action user must be able to take]"
|
||||
success_criteria: "[How we know they can do it]"
|
||||
business_impact:
|
||||
connection: "[How this action drives the business goal]"
|
||||
logic: "[Action → Outcome → Goal]"
|
||||
user_motivation:
|
||||
positive_driver: "[How action satisfies their wish]"
|
||||
negative_driver: "[How action addresses their fear]"
|
||||
essential_information:
|
||||
- "[Information element 1 — WHY needed for action]"
|
||||
- "[Information element 2 — WHY needed for action]"
|
||||
- "[Information element 3 — WHY needed for action]"
|
||||
cut_list:
|
||||
- "[Nice-to-know info that doesn't enable action]"
|
||||
- "[Impressive but irrelevant content]"
|
||||
action_barriers:
|
||||
- barrier: "[e.g., confusion about next steps]"
|
||||
solution: "[Content that removes this barrier]"
|
||||
- barrier: "[e.g., fear of commitment]"
|
||||
solution: "[Content that addresses this fear]"
|
||||
```
|
||||
|
||||
### 7. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save action filter, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the action filter is documented will you load {nextStepFile} to begin framing user empowerment.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Specific action identified (not vague "understanding")
|
||||
- Action connects to Trigger Map business goal
|
||||
- Action satisfies user's driving forces
|
||||
- Essential information determined (what enables the action)
|
||||
- Unnecessary information identified (what does not enable action)
|
||||
- Action barriers identified and addressed
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Accepting vague goals like "learn about us"
|
||||
- Generating content text in this step
|
||||
- Not challenging nice-to-know content
|
||||
- Proceeding without a specific required action
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,167 @@
|
||||
---
|
||||
name: 'step-04-empowerment-frame'
|
||||
description: 'Apply Badass Users principles to frame content around user capability and transformation'
|
||||
nextStepFile: './step-05-structural-order.md'
|
||||
---
|
||||
|
||||
# Step 4: Frame User Empowerment
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply Kathy Sierra's Badass Users framework to frame content around user capability and transformation — making users feel capable, showing their transformation path, creating "aha moments," and reducing cognitive load.
|
||||
|
||||
## 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 strategic content analyst applying Badass Users methodology
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring empowerment framing expertise, user brings their audience understanding
|
||||
- ✅ Maintain a user-centric, empowering tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on empowerment framing — transformation, capability, cognitive load
|
||||
- 🚫 FORBIDDEN to generate content text in this step
|
||||
- 💬 Reframe all feature-focused language to capability-focused language
|
||||
- 📋 All five Badass Users principles must be addressed
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document empowerment framing in structured format
|
||||
- 📖 Reference Badass Users principles data file when needed
|
||||
- 🚫 FORBIDDEN to proceed without transformation and capability framing defined
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3)
|
||||
- Focus: Framing content around user capability, not product features
|
||||
- Limits: Do not write content — define the empowerment frame for it
|
||||
- Dependencies: Action Filter from Step 3
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Define Current vs. Badass State
|
||||
|
||||
Ask: **"What's the user's CURRENT state?"** — What are they struggling with? How do they feel?
|
||||
|
||||
Ask: **"What's their BADASS state after success?"** — What will they be able to do? How will they feel?
|
||||
|
||||
### 2. Identify the "Aha Moment"
|
||||
|
||||
Ask: **"What insight or realization will make them say 'Oh! I get it!'?"**
|
||||
|
||||
The aha moment is a perspective shift, not just understanding. It unlocks confidence.
|
||||
|
||||
### 3. Frame Around Capability
|
||||
|
||||
Ask: **"How do we frame this content to highlight THEIR capability, not our features?"**
|
||||
|
||||
Transform feature-focused language to capability-focused language:
|
||||
- Before: "Our AI analyzes 10,000 sources"
|
||||
- After: "You'll spot trends before your competitors"
|
||||
|
||||
### 4. Show the Transformation Path
|
||||
|
||||
Ask: **"How do we make the transformation visible and achievable?"**
|
||||
|
||||
Users need to see where they are, where they are going, and that the path is real and manageable. Use specific numbers, social proof, and quick wins.
|
||||
|
||||
### 5. Reduce Cognitive Load
|
||||
|
||||
Ask: **"Where might this content overwhelm or confuse?"**
|
||||
|
||||
Look for: too many choices, too much jargon, too many steps, unclear next actions. Identify what to simplify or cut.
|
||||
|
||||
### 6. Focus on Skills Over Tools
|
||||
|
||||
Ask: **"What skill or capability are we helping them develop?"**
|
||||
|
||||
Not "using our platform" but "staying current effortlessly" or "becoming the local authority."
|
||||
|
||||
### 7. Document Empowerment Frame
|
||||
|
||||
```yaml
|
||||
empowerment_frame:
|
||||
transformation:
|
||||
current_state:
|
||||
description: "[Where user is now]"
|
||||
feelings: ["frustrated", "uncertain", "behind"]
|
||||
capabilities: "[What they can't do yet]"
|
||||
badass_state:
|
||||
description: "[Where they're going]"
|
||||
feelings: ["confident", "capable", "ahead"]
|
||||
capabilities: "[What they'll be able to do]"
|
||||
visibility: "[How we make the transformation visible and achievable]"
|
||||
aha_moment:
|
||||
insight: "[Key realization that shifts perspective]"
|
||||
why_powerful: "[Why this unlocks confidence]"
|
||||
capability_framing:
|
||||
- feature: "[Product feature]"
|
||||
reframed: "[What USER can do because of it]"
|
||||
- feature: "[Product feature]"
|
||||
reframed: "[What USER can do because of it]"
|
||||
cognitive_load:
|
||||
potential_issues:
|
||||
- issue: "[Where content might overwhelm]"
|
||||
solution: "[How we reduce load]"
|
||||
simplifications:
|
||||
- "[What we simplified or cut]"
|
||||
skill_focus:
|
||||
primary_skill: "[Main capability user develops]"
|
||||
supporting_skills: ["[Related capabilities]"]
|
||||
tools_secondary: "[Tools are means to skill, not the focus]"
|
||||
```
|
||||
|
||||
### 8. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save empowerment frame, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the empowerment frame is documented will you load {nextStepFile} to begin determining structural order.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Current state clearly defined
|
||||
- Badass state clearly defined
|
||||
- "Aha moment" identified
|
||||
- Content framed around user capability (not features)
|
||||
- Transformation path visible and achievable
|
||||
- Cognitive load issues identified and addressed
|
||||
- Focus on skills gained, not tools used
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating content text in this step
|
||||
- Leaving content framed around product features
|
||||
- Not identifying the "aha moment"
|
||||
- Skipping cognitive load analysis
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,174 @@
|
||||
---
|
||||
name: 'step-05-structural-order'
|
||||
description: 'Apply the Golden Circle to create persuasive WHY-HOW-WHAT content flow'
|
||||
nextStepFile: './step-06-generate-content.md'
|
||||
---
|
||||
|
||||
# Step 5: Determine Structural Order
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply Simon Sinek's Golden Circle to sequence all content from previous steps into a persuasive WHY-HOW-WHAT flow that moves users emotionally first, then logically, then to action.
|
||||
|
||||
## 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 strategic content architect applying Golden Circle methodology
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring structural persuasion expertise, user brings their content priorities
|
||||
- ✅ Maintain a clear, structured tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus ONLY on sequencing content into WHY-HOW-WHAT structure
|
||||
- 🚫 FORBIDDEN to generate final content text in this step
|
||||
- 💬 Map all essential information from previous steps to WHY, HOW, or WHAT
|
||||
- 📋 Validate the persuasive flow end-to-end before proceeding
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Document the structural order in structured format
|
||||
- 📖 Reference all content elements from Steps 3-4 (Action Filter + Empowerment Frame)
|
||||
- 🚫 FORBIDDEN to proceed without a validated WHY-HOW-WHAT structure
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3), Empowerment Frame (Step 4)
|
||||
- Focus: Sequencing existing content elements into persuasive order
|
||||
- Limits: Do not write final content — organize the structure for it
|
||||
- Dependencies: All previous steps provide the content elements to sequence
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Identify the WHY
|
||||
|
||||
Ask: **"What's the emotional opening that connects to their driving forces?"**
|
||||
|
||||
Opens with user's current emotional state, connects to driving forces from the Trigger Map, makes them care before explaining the solution.
|
||||
|
||||
### 2. Identify the HOW
|
||||
|
||||
Ask: **"What's the method that bridges emotional need to specific solution?"**
|
||||
|
||||
Explains the approach, shows how transformation happens, uses capability framing from Step 4, contains the "aha moment" insight.
|
||||
|
||||
### 3. Identify the WHAT
|
||||
|
||||
Ask: **"What are the concrete specifics and call to action?"**
|
||||
|
||||
Names the product/offer, provides social proof, clear CTA with capability framing, risk removal.
|
||||
|
||||
### 4. Map Content to Structure
|
||||
|
||||
Present all content elements from Steps 3-4. Work together to assign each piece to WHY (emotional opening), HOW (method/bridge), or WHAT (specifics/proof).
|
||||
|
||||
### 5. Sequence Within Sections
|
||||
|
||||
Within each section, determine the most persuasive order:
|
||||
|
||||
- **WHY section:** Problem → Validation → Aspiration
|
||||
- **HOW section:** Approach → Differentiator → Transformation
|
||||
- **WHAT section:** Naming → Proof → Action → Risk Removal
|
||||
|
||||
### 6. Validate Persuasive Flow
|
||||
|
||||
Ask: **"Does WHY → HOW → WHAT create natural emotional → logical → action flow?"**
|
||||
|
||||
- Can user understand WHY without knowing WHAT yet?
|
||||
- Does HOW bridge the gap naturally?
|
||||
- Does WHAT feel like a natural conclusion (not premature)?
|
||||
|
||||
### 7. Document Structural Order
|
||||
|
||||
```yaml
|
||||
structural_order:
|
||||
section_why:
|
||||
purpose: "Emotional truth / Why user should care"
|
||||
content_elements:
|
||||
- order: 1
|
||||
element: "[Opening hook]"
|
||||
rationale: "[Why this opens]"
|
||||
- order: 2
|
||||
element: "[Validation or aspiration]"
|
||||
rationale: "[Why this comes second]"
|
||||
section_how:
|
||||
purpose: "Method / Bridge from emotion to specifics"
|
||||
content_elements:
|
||||
- order: 1
|
||||
element: "[Solution approach]"
|
||||
rationale: "[Why this bridges first]"
|
||||
- order: 2
|
||||
element: "[Key differentiator]"
|
||||
rationale: "[Why this matters here]"
|
||||
- order: 3
|
||||
element: "[Transformation path]"
|
||||
rationale: "[Why this comes last in HOW]"
|
||||
section_what:
|
||||
purpose: "Specifics / Proof / Action"
|
||||
content_elements:
|
||||
- order: 1
|
||||
element: "[Product/offer name]"
|
||||
rationale: "[Why we can name it now]"
|
||||
- order: 2
|
||||
element: "[Social proof]"
|
||||
rationale: "[Why proof comes here]"
|
||||
- order: 3
|
||||
element: "[CTA]"
|
||||
rationale: "[Why action comes last]"
|
||||
flow_validation:
|
||||
feels_natural: "[yes/no + notes]"
|
||||
persuasive_arc: "[Does WHY → HOW → WHAT create emotional → logical → action flow?]"
|
||||
```
|
||||
|
||||
### 8. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Save structural order, then load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-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 end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the structural order is documented will you load {nextStepFile} to begin generating and reviewing content.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- WHY is identified (emotional opening, purpose)
|
||||
- HOW is identified (method, bridge, differentiator)
|
||||
- WHAT is identified (specifics, proof, CTA)
|
||||
- All essential information assigned to WHY, HOW, or WHAT
|
||||
- Content sequenced within each section
|
||||
- Flow feels natural and persuasive
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating final content text in this step
|
||||
- Putting WHAT before WHY (salesy, pushy)
|
||||
- Missing the WHY section entirely (cold, transactional)
|
||||
- Not mapping all essential information to a section
|
||||
- Not waiting for user input at menu
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,135 @@
|
||||
---
|
||||
name: 'step-06-generate-content'
|
||||
description: 'Generate strategically grounded content variations, review, and finalize'
|
||||
workflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 6: Generate and Review Content
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Generate 2-3 strategically grounded content variations based on all strategic context from Steps 0-5, guide user through selection and refinement, and produce the final content with full strategic traceability.
|
||||
|
||||
## 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 strategic content creator synthesizing all previous analysis
|
||||
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring content synthesis expertise, user brings final creative direction
|
||||
- ✅ Maintain a creative yet strategic tone
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Generate content variations that differ in driving force emphasis, not random rewrites
|
||||
- 🚫 FORBIDDEN to skip strategic traceability in the final output
|
||||
- 💬 Present each variation with clear rationale for strategic choices
|
||||
- 📋 Verify final content against all strategic context (Steps 0-5)
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Follow the Sequence of Instructions exactly
|
||||
- 💾 Save final content with strategic traceability using content-output template
|
||||
- 📖 Reference generation instructions data file for detailed variation guidance
|
||||
- 🚫 FORBIDDEN to finalize without user review and confirmation
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All outputs from Steps 0-5 (Purpose, Trigger Map, Awareness, Action, Empowerment, Structure)
|
||||
- Focus: Synthesizing strategy into actual content text, then refining with user
|
||||
- Limits: Variations are strategic alternatives, not random drafts
|
||||
- Dependencies: Complete WHY-HOW-WHAT structure from Step 5
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Synthesize All Context
|
||||
|
||||
Review and synthesize all strategic outputs from Steps 0-5 before generating.
|
||||
|
||||
### 2. Generate 2-3 Variations
|
||||
|
||||
Create variations that differ in which driving forces they emphasize:
|
||||
- **Variation A (Wish-focused):** Emphasizes positive driving force / aspiration
|
||||
- **Variation B (Fear-focused):** Emphasizes negative driving force / pain avoidance
|
||||
- **Variation C (Balanced):** Blends both, may shift awareness emphasis
|
||||
|
||||
Present each with clear rationale explaining strategic choices.
|
||||
|
||||
### 3. Gather Initial Reaction
|
||||
|
||||
Ask: **"Which variation resonates most with you?"** Allow selection, combination, or element picking across variations.
|
||||
|
||||
### 4. Alignment Check
|
||||
|
||||
Ask: **"Does this feel aligned with the strategic context?"**
|
||||
|
||||
Check against: Trigger Map business goal, driving forces, awareness level, required action, capability framing, WHY-HOW-WHAT structure.
|
||||
|
||||
### 5. Refinement
|
||||
|
||||
Ask: **"What would you adjust or combine?"** Guide through specific changes: headline from A but body from B, stronger emphasis on X, softer tone on Y.
|
||||
|
||||
### 6. Verify Completeness
|
||||
|
||||
Ask: **"Is anything missing that we identified in previous steps?"** Check against essential information (Step 3), barriers (Step 3), aha moment (Step 4), cognitive load reductions (Step 4).
|
||||
|
||||
### 7. Validate Awareness Journey
|
||||
|
||||
Ask: **"Does this move the user from START to END awareness?"** Verify the journey is smooth, not jarring.
|
||||
|
||||
### 8. Document Final Content
|
||||
|
||||
Save using content-output template with full strategic traceability:
|
||||
- Trigger Map reference, awareness journey, action enabled, empowerment achieved
|
||||
- Implementation notes (technical, design, language tags, asset needs)
|
||||
|
||||
### 9. Present MENU OPTIONS
|
||||
|
||||
Display: **"Select an Option:** [M] Return to Activity Menu"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF M: Save final content, update design log, return to Activity Menu in {workflowFile}
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#9-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- User can chat or ask questions — always respond and then end with display again of the menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the final step of the Content Creation workflow. When M is selected and final content is saved with traceability, return to the Activity Menu.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Multiple variations generated with clear rationale
|
||||
- Strategic choices explained and visible
|
||||
- User reviewed and selected/combined approach
|
||||
- Final content aligns with all strategic context (Steps 0-5)
|
||||
- Required action is enabled
|
||||
- Awareness journey is smooth
|
||||
- Strategic traceability documented
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Generating only one variation without alternatives
|
||||
- Not explaining strategic choices per variation
|
||||
- Skipping traceability documentation
|
||||
- Finalizing without user confirmation
|
||||
- Not checking against all previous step outputs
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
Reference in New Issue
Block a user