convoke-agents 2.0.0

package/_bmad/bme/_vortex/workflows/behavior-analysis/steps/step-05-synthesize.md

@@ -0,0 +1,174 @@
+---
+step: 5
+workflow: behavior-analysis
+title: Synthesize & Route
+---
+
+# Step 5: Synthesize & Route
+
+Time to bring everything together. We've validated the experiment context, extracted baselines, classified behavior patterns, and gathered supporting evidence. Now we produce the HC5 Behavioral Signal Report artifact and route to the next step in the Vortex.
+
+## Why This Matters
+
+Production data is the most honest user feedback — it can't lie. But raw behavior data isn't intelligence. Intelligence is behavior classified through experiment baselines, supported by evidence, and packaged for the decision-maker. The HC5 artifact gives Max everything needed to make evidence-based decisions: what behavior was observed, how it compares to experiment baselines, whether it's variance, regression, or discovery, and how strong the evidence is. No recommendations. No strategy. Just classified behavioral intelligence.
+
+## Your Task
+
+### 1. Review Your Behavioral Signal Report
+
+Before we package everything, let's do a final quality pass on each section:
+
+**Signal Description:**
+
+| Field | Check |
+|-------|-------|
+| **Signal Summary** | Is it factual and one sentence? Does it capture the behavioral pattern, not just a metric? |
+| **Signal Type** | Is the classification accurate? For behavior analysis, type will typically be `Behavior Pattern`. |
+| **Severity** | Is the severity justified by the classification? Regressions typically warrant `Warning` or `Critical`; variance is typically `Informational`. |
+| **Detection Method** | Is it clear how this behavior came to attention? |
+| **Time Window** | Is the observation period precisely defined? |
+| **Affected Scope** | Are the affected users/segments/features clearly identified? |
+
+**Context (Experiment Lineage + Vortex History):**
+
+| Field | Check |
+|-------|-------|
+| **Experiment Lineage** | Can the behavior be traced back to its originating experiment? Are the baselines explicit? |
+| **Vortex History** | Are available upstream references (HC2, HC3, previous HC5) documented? |
+
+**Trend Analysis:**
+
+| Field | Check |
+|-------|-------|
+| **Trend Direction** | Does the classification map to a clear trend? Regression = `Degrading`, Variance = `Stable`, Novel = context-dependent. |
+| **Rate of Change** | Is it quantified with specific metrics, not vague descriptions? |
+| **Baseline Comparison** | Is the experiment baseline explicitly stated and the comparison clear? |
+| **Confidence** | Does the confidence level reflect both data quality and classification certainty? |
+
+**Anomaly Detection (for Novel Behavior classifications):**
+
+| Field | Check |
+|-------|-------|
+| **Anomaly Description** | Is the novel behavior described factually, without speculative strategy? |
+| **Discovery Needed** | Is the HC10 routing decision documented with rationale? |
+
+**Data Quality:**
+
+| Field | Check |
+|-------|-------|
+| **Sample Size** | Is it sufficient for the classifications made? |
+| **Confidence Level** | Does it honestly reflect data reliability for this behavioral analysis? |
+
+### 2. Generate the HC5 Artifact
+
+I'll produce the HC5 Behavioral Signal Report artifact with this structure:
+
+```yaml
+---
+contract: HC5
+type: artifact
+source_agent: noah
+source_workflow: behavior-analysis
+target_agents: [max]
+input_artifacts:
+  - path: "_bmad-output/vortex-artifacts/{your-hc4-artifact}"
+    contract: HC4
+created: YYYY-MM-DD
+---
+```
+
+**HC5 Required Body Sections:**
+1. **Signal Description** — Signal Summary, Signal Type (`Behavior Pattern`), Severity, Detection Method, Time Window, Affected Scope
+2. **Context** — Experiment Lineage (Originating Experiment, Original Hypothesis, Experiment Outcome, Expected Production Behavior, Actual vs Expected) + Vortex History (Problem Definition, Hypothesis Origin, Previous Signals, Related Experiments)
+3. **Trend Analysis** — Trend Direction, Trend Duration, Rate of Change, Baseline Comparison, Confidence
+4. **Anomaly Detection** (when novel behavior detected) — Anomaly Description, Deviation from Expected, Potential Explanations, Discovery Needed, Discovery Focus
+5. **Data Quality** — Sample Size, Data Completeness, Known Biases, Confidence Level
+
+**Behavior Classification Addendum:**
+In addition to the standard HC5 sections, include a Behavior Classification Summary showing each classified pattern with its category (Expected Variance / Regression / Novel Behavior), supporting evidence, and confidence level. This gives Max the behavioral context that distinguishes this report from a standard signal report.
+
+**This artifact explicitly does NOT include:**
+- Strategic recommendations (that is Max's domain)
+- Pivot/patch/persevere decisions (that is Max's domain)
+- Experiment design suggestions (that is Liam/Wade's domain)
+- Resource allocation recommendations (that is Max's domain)
+
+Noah produces intelligence — contextual, evidence-based behavioral classification. Max produces decisions.
+
+**Save to:** `{output_folder}/vortex-artifacts/hc5-behavior-report-{date}.md`
+
+I'll create this file with all the sections above once you confirm the content is ready.
+
+### 3. Validation Questions
+
+Before we finalize, let's validate:
+
+**Evidence Check:**
+- [ ] Is every classification grounded in observed behavior compared to experiment baselines?
+- [ ] Can we trace the behavior back to its originating experiment through the Experiment Lineage section?
+- [ ] Is the evidence for each classification quantified with specific metrics?
+
+**Classification Check:**
+- [ ] Does every classified behavior fit clearly into one category (Expected Variance, Regression, or Novel)?
+- [ ] Is the classification supported by the baseline comparison, not by assumption?
+- [ ] Are borderline cases acknowledged with appropriate confidence levels?
+
+**Completeness Check:**
+- [ ] Does the Signal Description include all 6 required fields?
+- [ ] Does the Context section include Experiment Lineage with all 5 required fields?
+- [ ] Does the Trend Analysis include all 5 required fields?
+- [ ] Does the Data Quality section include all required fields?
+- [ ] If novel behavior was detected, does Anomaly Detection include all required fields?
+
+**Intelligence-Not-Strategy Check:**
+- [ ] Does the report contain zero strategic recommendations?
+- [ ] Does it avoid prescribing what to do about the classified behavior?
+- [ ] Does it present findings in classification + evidence + trend format, leaving decisions to Max?
+- [ ] Would Max have everything needed to make an informed decision from this report?
+
+---
+
+## Your Turn
+
+Review the behavioral signal report sections. Confirm when you're ready for me to generate the final HC5 artifact.
+
+---
+
+**[a]** Advanced Elicitation — Deep dive into HC5 refinement with guided questioning
+**[p]** Party Mode — Bring in other Vortex agents for collaborative artifact critique
+**[c]** Continue — Generate the HC5 artifact and proceed to routing
+
+---
+
+## Vortex Compass
+
+Based on what you just completed, here are your evidence-driven options:
+
+| If you learned... | Consider next... | Agent | Why |
+|---|---|---|---|
+| Behavioral signal report complete with classified patterns and evidence | pivot-patch-persevere | Max 🧭 | Behavioral signal report triggers decision (HC5) |
+| ⚡ Novel behavior detected not covered by original hypothesis | user-discovery | Isla 🔍 | Novel behavior warrants discovery research (HC10) |
+| Specific signal within behavior patterns warrants deeper analysis | signal-interpretation | Noah 📡 | Deeper signal analysis needed |
+
+> **Note:** These are evidence-based recommendations. You can navigate to any Vortex agent
+> at any time based on your judgment.
+
+**Or run Max's [VN] Vortex Navigation** for a full gap analysis across all streams.
+
+### ⚠️ Insufficient Evidence for Routing
+
+If the evidence gathered so far doesn't clearly point to a single next step:
+
+| To route to... | You need... |
+|----------------|-------------|
+| Max 🧭 | Complete HC5 behavioral signal report with classified behavior patterns and sufficient evidence |
+| Isla 🔍 | Specific novel behavior identified with clear deviation from experiment expectations |
+| Noah 📡 | Specific signal identified within behavior patterns that warrants focused signal-interpretation analysis |
+
+**Workflow-specific signals:**
+- Classification unclear → consider revisiting **step-03** for sharper analysis against baselines
+- Cannot establish experiment baselines → consider revisiting **step-02** for deeper baseline extraction
+- Evidence insufficient for classification → gather more production behavior data before proceeding
+- Behavior observed but cannot connect to any experiment → consider whether this should be a signal-interpretation workflow instead
+
+**Recommended:** Revisit earlier steps to strengthen your behavioral analysis, or run **Max's [VN] Vortex Navigation** for a full gap analysis.

package/_bmad/bme/_vortex/workflows/behavior-analysis/workflow.md

@@ -0,0 +1,52 @@
+---
+workflow: behavior-analysis
+type: step-file
+description: Analyze production behavior patterns against validated experiment baselines to classify variance, regression, or novel behavior
+author: Noah (production-intelligence-specialist)
+version: 1.6.0
+---
+
+# Behavior Analysis Workflow
+
+This workflow guides you through analyzing production behavior patterns by comparing them to validated experiment baselines, classifying what the behavior means, and producing an HC5 behavioral signal report for Max.
+
+## What is Behavior Analysis?
+
+Behavior analysis is the practice of reading production behavior through experiment baselines — not as isolated user actions, but as patterns measured against what was predicted and validated.
+
+Behavioral patterns reveal intent that surveys miss. A user segment abandoning a feature could be a regression from validated performance, normal variance within expected tolerance, or novel behavior the experiment never anticipated. The classification depends entirely on the experiment baselines: what was tested, what was confirmed, and what behavior was expected in production.
+
+This workflow compares observed production behavior to experiment baselines, classifies each pattern into one of three categories — expected variance, regression, or novel behavior — and packages the classification as intelligence for the decision-maker. Here's what we're seeing in context: that's the deliverable. Not strategy. Not recommendations. Classified behavioral intelligence.
+
+## Workflow Structure
+
+**Step-file architecture:**
+- Just-in-time loading (each step loads only when needed)
+- Sequential enforcement (must complete step N before step N+1)
+- State tracking in frontmatter (progress preserved)
+
+## Steps Overview
+
+1. **Setup & Input Validation** - Validate experiment context input (HC4 artifact or equivalent) and behavior observation
+2. **Experiment Baselines & Behavior Observation** - Extract validated baselines and document the observed behavior
+3. **Behavior Pattern Classification** - Classify behavior as expected variance, regression, or novel behavior
+4. **Evidence Gathering & Data Quality** - Build the evidence base for each classification and assess data reliability
+5. **Synthesize & Route** - Produce HC5 behavioral signal report artifact and route via Compass
+
+## Output
+
+**Artifact:** HC5 Behavioral Signal Report markdown file in `{output_folder}/vortex-artifacts/hc5-behavior-report-{date}.md`
+
+**Template:** None (HC5 artifact is generated inline during Step 5)
+
+**Schema:** Conforms to HC5 contract (`_bmad/bme/_vortex/contracts/hc5-signal-report.md`)
+
+**Consumer:** Max (pivot-patch-persevere) uses this to make evidence-based decisions about behavioral signals in production.
+
+---
+
+## INITIALIZATION
+
+Load config from {project-root}/_bmad/bme/_vortex/config.yaml
+
+Load step: {project-root}/_bmad/bme/_vortex/workflows/behavior-analysis/steps/step-01-setup.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/contextualize-scope.template.md

@@ -0,0 +1,67 @@
+---
+title: "Scope Decision: {scope-name}"
+date: {date}
+created-by: {user-name} with Emma (contextualization-expert)
+type: scope-decision
+status: DECIDED
+version: 1.0
+---
+
+# Scope Decision: {scope-name}
+
+## Decision Summary
+
+**Selected Problem Space:** {selected-scope}
+
+**Rationale:** {selection-rationale}
+
+**De-scoped (Not Now):** {descoped-problems}
+
+---
+
+## Problem Opportunities Considered
+
+{opportunities-list}
+
+---
+
+## Evaluation Criteria
+
+{criteria-list}
+
+---
+
+## Scoring Matrix
+
+{scoring-matrix}
+
+---
+
+## Selected Scope
+
+### Problem Space
+{problem-space}
+
+### Boundaries (What's In)
+{scope-in}
+
+### Boundaries (What's Out)
+{scope-out}
+
+---
+
+## Strategic Fit
+
+{strategic-fit-analysis}
+
+---
+
+## Next Steps
+
+{next-steps}
+
+---
+
+**Created with:** Convoke v2.0.0 - Vortex Pattern (Contextualize Stream)
+**Agent:** Emma (Contextualization Expert)
+**Workflow:** contextualize-scope

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-01-list-opportunities.md

@@ -0,0 +1,47 @@
+---
+step: 1
+workflow: contextualize-scope
+title: List Problem Opportunities
+---
+
+# Step 1: List Problem Opportunities
+
+What problems could you solve? Let's get them all on the table before deciding.
+
+## Why This Matters
+
+You can't make a good decision without seeing all options. Listing opportunities ensures you don't miss something important.
+
+## Your Task
+
+List 3-7 problem opportunities you could investigate. For each, provide:
+
+### 1. Problem name (short label)
+### 2. Problem description (1-2 sentences)
+### 3. Who experiences this problem?
+### 4. Rough market size estimate
+### 5. Initial gut feeling (High/Medium/Low interest)
+
+## Example
+
+**Opportunity A: Team Status Visibility**
+- Remote managers lack real-time visibility into distributed team progress
+- Managers of 5-20 person distributed software teams
+- ~2M teams globally, $15B TAM
+- Interest: HIGH
+
+**Opportunity B: Meeting Overload**
+- Teams waste 10+ hours/week in unnecessary meetings
+- Knowledge workers at companies 50-500 employees
+- ~10M workers globally, $50B TAM
+- Interest: MEDIUM
+
+---
+
+## Your Turn
+
+List your problem opportunities.
+
+## Next Step
+
+{project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-02-define-criteria.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-02-define-criteria.md

@@ -0,0 +1,36 @@
+---
+step: 2
+workflow: contextualize-scope
+title: Define Evaluation Criteria
+---
+
+# Step 2: Define Evaluation Criteria
+
+How will you decide which problem to pursue?
+
+## Your Task
+
+Define 3-5 criteria for evaluating opportunities. Common criteria:
+
+- **Impact:** How many people does this affect? How painful is it?
+- **Feasibility:** Can we actually build this? Do we have the expertise?
+- **Strategic Fit:** Does this align with our vision and strengths?
+- **Market Opportunity:** Size of market? Willingness to pay?
+- **Time to Value:** How quickly can we validate this?
+
+## Example
+
+1. **Impact** (Weight: 30%) - Number of users × problem intensity
+2. **Feasibility** (Weight: 25%) - Team expertise + technical complexity
+3. **Strategic Fit** (Weight: 25%) - Alignment with long-term vision
+4. **Speed to Validation** (Weight: 20%) - Can we test this in <3 months?
+
+---
+
+## Your Turn
+
+Define your evaluation criteria with weights.
+
+## Next Step
+
+{project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-03-evaluate-opportunities.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-03-evaluate-opportunities.md

@@ -0,0 +1,30 @@
+---
+step: 3
+workflow: contextualize-scope
+title: Evaluate Each Opportunity
+---
+
+# Step 3: Evaluate Each Opportunity
+
+Score each opportunity against your criteria.
+
+## Your Task
+
+For each opportunity, score 1-10 on each criterion. Calculate weighted scores.
+
+## Example
+
+| Opportunity | Impact | Feasibility | Strategic Fit | Speed | Total |
+|------------|--------|-------------|---------------|-------|-------|
+| Team Status| 9      | 8           | 9             | 7     | 8.25  |
+| Meetings   | 7      | 6           | 5             | 8     | 6.45  |
+
+---
+
+## Your Turn
+
+Score your opportunities.
+
+## Next Step
+
+{project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-04-define-boundaries.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-04-define-boundaries.md

@@ -0,0 +1,32 @@
+---
+step: 4
+workflow: contextualize-scope
+title: Define Scope Boundaries
+---
+
+# Step 4: Define Scope Boundaries
+
+What's IN scope? What's OUT?
+
+## Your Task
+
+Define clear boundaries:
+
+### What's IN Scope
+- Which user segment?
+- Which use cases?
+- Which geography/market?
+
+### What's OUT of Scope
+- What are you explicitly NOT solving?
+- What's phase 2 or phase 3?
+
+---
+
+## Your Turn
+
+Define your scope boundaries.
+
+## Next Step
+
+{project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-05-validate-fit.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-05-validate-fit.md

@@ -0,0 +1,28 @@
+---
+step: 5
+workflow: contextualize-scope
+title: Validate Strategic Fit
+---
+
+# Step 5: Validate Strategic Fit
+
+Does this choice align with your vision, team, and resources?
+
+## Your Task
+
+Validate fit across dimensions:
+
+1. **Vision Alignment:** Does this serve your product vision?
+2. **Team Capabilities:** Do you have the skills to execute?
+3. **Resource Requirements:** Can you afford to investigate this?
+4. **Market Timing:** Is now the right time?
+
+---
+
+## Your Turn
+
+Validate strategic fit.
+
+## Next Step
+
+{project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-06-synthesize.md

package/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-06-synthesize.md

@@ -0,0 +1,36 @@
+---
+step: 6
+workflow: contextualize-scope
+title: Synthesize
+---
+
+# Step 6: Synthesize
+
+Create the final scope decision document.
+
+## Your Task
+
+Provide final decision summary:
+
+1. **Selected scope** and why
+2. **De-scoped opportunities** and why not now
+3. **Next steps** (suggested: lean-persona → mvp → lean-experiment)
+
+---
+
+## Workflow Complete
+
+## Vortex Compass
+
+Based on what you just completed, here are your evidence-driven options:
+
+| If you learned... | Consider next... | Agent | Why |
+|---|---|---|---|
+| Scope is defined, users unknown | lean-persona | Emma 🎯 | Understand who exists in this problem space |
+| Scope chosen, need user validation | user-interview | Isla 🔍 | Confirm real users care about this scope |
+| Ready to test assumptions | mvp | Wade 🧪 | Design the smallest test for your scope decision |
+
+> **Note:** These are evidence-based recommendations. You can navigate to any Vortex agent
+> at any time based on your judgment.
+
+**Or run Max's [VN] Vortex Navigation** for a full gap analysis across all streams.

package/_bmad/bme/_vortex/workflows/contextualize-scope/validate.md

@@ -0,0 +1,30 @@
+# Validate Scope Decision
+
+**Status:** Coming in v1.2.0
+
+**Agent:** Emma (Contextualization Expert)
+
+**Stream:** Contextualize
+
+## Overview
+
+This validation workflow helps you review scope decisions to ensure they're data-driven and strategically sound.
+
+## What Gets Validated
+
+- Are all relevant opportunities considered?
+- Are evaluation criteria clear and measurable?
+- Is scoring consistent across opportunities?
+- Is the decision rationale well-documented?
+- Are de-scoped opportunities captured for future reference?
+- Does this align with product vision?
+
+## Coming in v1.2.0
+
+This validation workflow will be available alongside the contextualize-scope workflow in March 2026.
+
+## Questions?
+
+For questions or to request early access:
+- GitHub Issues: https://github.com/amalik/convoke-agents/issues
+- Tag with: `workflow:contextualize-scope` and `v1.2.0`

package/_bmad/bme/_vortex/workflows/contextualize-scope/workflow.md

@@ -0,0 +1,59 @@
+---
+workflow: contextualize-scope
+type: step-file
+description: Decide which problem space to investigate using strategic evaluation
+author: Emma (contextualization-expert)
+version: 1.2.0
+---
+
+# Contextualize Scope Workflow
+
+This workflow guides you through deciding which problem space to investigate by evaluating opportunities systematically.
+
+## What is Scope Contextualization?
+
+Scope contextualization is the strategic decision of where to focus your investigation. You likely have multiple problems you could solve - this workflow helps you choose wisely by:
+
+- **Identifying all opportunities** - What problems are on the table?
+- **Defining evaluation criteria** - What matters most (impact, feasibility, strategic fit)?
+- **Scoring systematically** - Rate each opportunity against criteria
+- **Deciding with rationale** - Choose one, document why
+- **De-scoping intentionally** - Say "no" to others (for now)
+
+## Why This Matters
+
+Choosing the wrong problem space wastes months of effort. This workflow ensures:
+- You're solving a problem worth solving
+- You pick the problem you can actually solve
+- You don't spread resources across too many problems
+- You can defend your choice with evidence
+
+## Workflow Structure
+
+**Step-file architecture:**
+- Just-in-time loading (each step loads only when needed)
+- Sequential enforcement (must complete step N before step N+1)
+- State tracking in frontmatter (progress preserved)
+
+## Steps Overview
+
+1. **List Problem Opportunities** - What problems could you solve?
+2. **Define Evaluation Criteria** - How will you choose?
+3. **Evaluate Each Opportunity** - Score against criteria
+4. **Define Scope Boundaries** - What's in? What's out?
+5. **Validate Strategic Fit** - Does this align with vision/resources?
+6. **Synthesize** - Create scope decision document
+
+## Output
+
+**Artifact:** Scope decision document in `{output_folder}/scope-decision-{scope-name}-{date}.md`
+
+**Template:** Uses [contextualize-scope.template.md](contextualize-scope.template.md)
+
+---
+
+## INITIALIZATION
+
+Load config from {project-root}/_bmad/bme/_vortex/config.yaml
+
+Load step: {project-root}/_bmad/bme/_vortex/workflows/contextualize-scope/steps/step-01-list-opportunities.md