gaia-framework 1.57.0 → 1.57.2

package/_gaia/lifecycle/templates/test-plan-template.md

@@ -1,56 +0,0 @@
----
-template: 'test-plan'
-version: 1.0.0
-used_by: ['test-design']
----
-
-# Test Plan: {feature_name}
-
-> **Project:** {project_name}
-> **Date:** {date}
-> **Author:** {agent_name}
-
-## Scope
-
-{What is being tested and what is out of scope.}
-
-## Risk Assessment
-
-| Area | Risk Level | Coverage Strategy |
-|------|-----------|------------------|
-| {area} | {H/M/L} | {approach} |
-
-## Test Pyramid
-
-### Unit Tests
-
-| Component | Tests | Priority |
-|-----------|-------|----------|
-| {component} | {description} | {P0-P2} |
-
-### Integration Tests
-
-| Integration | Tests | Priority |
-|-------------|-------|----------|
-| {integration point} | {description} | {P0-P2} |
-
-### E2E Tests
-
-| Scenario | Steps | Priority |
-|----------|-------|----------|
-| {user flow} | {description} | {P0-P2} |
-
-## Test Data
-
-{Required test data, fixtures, or mocks.}
-
-## Environment
-
-{Test environment requirements and setup.}
-
-## Quality Gates
-
-- [ ] Unit test coverage >= {target}%
-- [ ] All P0 scenarios passing
-- [ ] No critical defects open
-- [ ] Performance within budget

package/_gaia/lifecycle/templates/ux-design-assessment-template.md

@@ -1,122 +0,0 @@
----
-template: 'ux-design-assessment'
-version: 1.0.0
-used_by: ['brownfield-onboarding']
----
-
-# UX Design Assessment: {product_name}
-
-> **Project:** {project_name}
-> **Date:** {date}
-> **Author:** {agent_name}
-> **Mode:** Brownfield — assessed from existing codebase
-
-## 1. UX Overview
-
-{Brief description of the application's user-facing surface: what type of UI, who uses it, primary user flows.}
-
-## 2. Existing UI Patterns
-
-### Component Library
-
-| Aspect | Detail |
-|--------|--------|
-| UI framework | {React / Angular / Vue / Flutter / SwiftUI / etc.} |
-| Component library | {Material UI / Ant Design / custom / none} |
-| Design system | {documented / partial / none} |
-| Styling approach | {CSS Modules / Tailwind / Styled Components / SCSS / etc.} |
-| Theming | {dark mode / custom themes / none} |
-
-### Layout Patterns
-
-| Pattern | Usage | Consistency |
-|---------|-------|-------------|
-| Page layout | {sidebar + content / top nav / etc.} | {consistent / varies} |
-| Grid system | {CSS Grid / Flexbox / framework grid} | {consistent / varies} |
-| Responsive design | {breakpoints defined / partial / not responsive} | {details} |
-| Spacing system | {design tokens / ad-hoc values} | {consistent / varies} |
-
-## 3. Navigation Structure
-
-```mermaid
-flowchart TD
-    HOME[Home/Dashboard]
-    HOME --> NAV1["{Section 1}"]
-    HOME --> NAV2["{Section 2}"]
-    HOME --> NAV3["{Section 3}"]
-    NAV1 --> SUB1["{Subsection}"]
-    NAV2 --> SUB2["{Subsection}"]
-```
-
-{Describe the navigation model: sidebar, top nav, breadcrumbs, tabs, routing structure.}
-
-## 4. Interaction Patterns
-
-### Forms
-
-| Pattern | Implementation | Consistency |
-|---------|---------------|-------------|
-| Form validation | {client-side / server-side / both} | {consistent / varies} |
-| Error display | {inline / toast / summary} | {consistent / varies} |
-| Submit handling | {optimistic / loading state / blocking} | {consistent / varies} |
-| Multi-step forms | {wizard / tabs / none} | {details} |
-
-### Modals & Dialogs
-
-| Pattern | Implementation | Consistency |
-|---------|---------------|-------------|
-| Confirmation dialogs | {standard pattern / ad-hoc} | {consistent / varies} |
-| Modal management | {portal / overlay / framework modal} | {consistent / varies} |
-| Keyboard handling | {Escape to close / focus trap / none} | {details} |
-
-### Notifications & Feedback
-
-| Pattern | Implementation | Consistency |
-|---------|---------------|-------------|
-| Success feedback | {toast / banner / inline} | {consistent / varies} |
-| Error feedback | {toast / modal / inline / error boundary} | {consistent / varies} |
-| Loading states | {skeleton / spinner / progress bar} | {consistent / varies} |
-| Empty states | {placeholder / illustration / message} | {consistent / varies} |
-
-## 5. Accessibility Assessment
-
-| Criteria | Status | Details |
-|----------|--------|---------|
-| Target WCAG level | {A / AA / AAA / Unknown} | {documented requirement or inferred} |
-| ARIA usage | {comprehensive / partial / minimal / none} | {examples} |
-| Semantic HTML | {consistent / partial / div-heavy} | {examples} |
-| Keyboard navigation | {full support / partial / broken} | {details} |
-| Focus management | {visible focus rings / custom / missing} | {details} |
-| Color contrast | {passes AA / fails / untested} | {details} |
-| Screen reader tested | {yes / no} | {details} |
-| a11y tooling | {axe / Lighthouse / pa11y / none} | {config path} |
-
-## 6. UX Gap Analysis
-
-| Gap | Severity | Affected Area | Current State | Desired State |
-|-----|----------|--------------|---------------|---------------|
-| {Missing responsive design} | {High / Medium / Low} | {pages affected} | {desktop only} | {responsive} |
-| {Inconsistent error handling} | {Medium} | {forms} | {varies by page} | {unified pattern} |
-| {Accessibility violations} | {High} | {navigation} | {no ARIA labels} | {WCAG AA} |
-
-## 7. Proposed UX Improvements
-
-{Only for gap features identified in the PRD. Do not propose changes to working, acceptable patterns.}
-
-### 7.1 {Improvement Area}
-
-- **Current state:** {what exists now}
-- **Proposed change:** {what should change}
-- **Rationale:** {why this matters for gap features}
-- **Affected components:** {list of components to modify}
-
-## 8. Wireframe Descriptions
-
-{Text-based descriptions of new or significantly modified screens for gap features only.}
-
-### 8.1 {Screen Name}
-
-- **Purpose:** {what this screen does}
-- **Layout:** {describe the layout structure}
-- **Key components:** {list the main UI elements}
-- **Interactions:** {describe key user interactions}

package/_gaia/lifecycle/workflows/1-analysis/advanced-elicitation/instructions.xml

@@ -1,44 +0,0 @@
-<workflow name="advanced-elicitation">
-<critical>
-  <mandate>Use structured questioning techniques from methods.csv</mandate>
-  <mandate>Document all requirements discovered with clear traceability</mandate>
-  <mandate>Distinguish between stated needs, implied needs, and assumed needs</mandate>
-</critical>
-<step n="1" title="Context Gathering">
-  <action>Load upstream research artifacts if available: project-brainstorm.md, market-research.md, domain-research.md, technical-research.md</action>
-  <action>Summarize what upstream context was found — present key themes, target users, market insights, and technical constraints already discovered</action>
-  <ask>Based on the research so far, what product or feature area do you want to explore deeper? (Or describe from scratch if no prior research exists)</ask>
-  <ask>Who are the key stakeholders?</ask>
-  <ask>Are there specific requirements gaps or assumptions from the research that you want to validate?</ask>
-</step>
-<step n="2" title="Method Selection">
-  <action>Load methods.csv to show available elicitation techniques</action>
-  <action>Present available methods with their descriptions and best-fit scenarios</action>
-  <ask>Which elicitation method(s) would you like to use? (or let me recommend based on your context)</ask>
-  <action>If user defers: recommend 2-3 methods based on the project context</action>
-</step>
-<step n="3" title="Elicitation Execution">
-  <action>For each selected method: execute the structured questioning flow</action>
-  <action>5 Whys: ask "why" iteratively to uncover root motivations</action>
-  <action>Socratic Method: challenge assumptions through guided questions</action>
-  <action>User Story Mapping: walk through the user journey end-to-end</action>
-  <action>MoSCoW: classify each requirement as Must/Should/Could/Won't</action>
-  <action>Kano Model: categorize features by satisfaction impact</action>
-  <action>Jobs-to-be-Done: identify the core job the user is hiring the product for</action>
-  <action>Assumption Mapping: list and validate all project assumptions</action>
-  <action>Stakeholder Mapping: identify all stakeholders and their needs</action>
-  <action>Document all requirements discovered during each method</action>
-</step>
-<step n="4" title="Requirements Synthesis">
-  <action>Consolidate all discovered requirements across methods</action>
-  <action>Remove duplicates and resolve conflicts</action>
-  <action>Categorize as: functional, non-functional, constraint, assumption</action>
-  <action>Tag each requirement with source method and confidence level</action>
-  <action>Identify gaps where further elicitation is needed</action>
-</step>
-<step n="5" title="Generate Output">
-  <template-output file="{planning_artifacts}/elicitation-report-{date}.md">
-    Generate elicitation report with: context summary, methods used, all discovered requirements (categorized), assumptions log, gaps identified, and recommended next steps.
-  </template-output>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/1-analysis/advanced-elicitation/methods.csv

@@ -1,9 +0,0 @@
-method,description,best_for,question_count
-"5 Whys","Ask 'why' repeatedly to find root cause","Understanding motivations and root problems",5
-"Socratic Method","Guided questioning to challenge assumptions","Validating requirements and uncovering gaps",8
-"User Story Mapping","Map user journey end-to-end","Understanding workflows and user needs",10
-"MoSCoW Prioritization","Must/Should/Could/Won't classification","Prioritizing features and requirements",6
-"Kano Model","Categorize features by satisfaction impact","Feature prioritization and delight factors",8
-"Jobs-to-be-Done","What job is the user hiring this product for","Understanding true user motivations",7
-"Assumption Mapping","List and validate all assumptions","Risk identification and validation planning",6
-"Stakeholder Mapping","Identify all stakeholders and their needs","Ensuring comprehensive requirements coverage",5

package/_gaia/lifecycle/workflows/1-analysis/advanced-elicitation/workflow.yaml

@@ -1,33 +0,0 @@
-# Advanced Elicitation Workflow
-# Deep requirements elicitation using structured questioning techniques
-# Phase 1 (Analysis) — optional deep-dive after research, before product brief
-
-name: advanced-elicitation
-display_name: "Advanced Requirements Elicitation"
-description: "Deep requirements elicitation using structured questioning techniques"
-module: lifecycle
-agent: orchestrator
-
-config_source: "{installed_path}/lifecycle/config.yaml"
-
-instructions: "{installed_path}/lifecycle/workflows/1-analysis/advanced-elicitation/instructions.xml"
-
-input_file_patterns:
-  brainstorm:
-    whole: "{planning_artifacts}/project-brainstorm.md"
-    load_strategy: "FULL_LOAD"
-  market_research:
-    whole: "{planning_artifacts}/market-research.md"
-    load_strategy: "FULL_LOAD"
-  domain_research:
-    whole: "{planning_artifacts}/domain-research.md"
-    load_strategy: "FULL_LOAD"
-  technical_research:
-    whole: "{planning_artifacts}/technical-research.md"
-    load_strategy: "FULL_LOAD"
-
-output:
-  primary: "{planning_artifacts}/elicitation-report-{date}.md"
-
-data_files:
-  methods: "{installed_path}/lifecycle/workflows/1-analysis/advanced-elicitation/methods.csv"

package/_gaia/lifecycle/workflows/1-analysis/brainstorm-project/checklist.md

@@ -1,24 +0,0 @@
----
-title: 'Brainstorm Project Validation'
-validation-target: 'Project brainstorm output'
-required-inputs: []
-validation-rules:
-  - 'Vision statement must be clearly articulated'
-  - 'At least 3 opportunity areas identified'
----
-## Vision Clarity
-- [ ] Business idea clearly articulated
-- [ ] Target users defined
-- [ ] Pain points identified
-- [ ] Differentiators stated
-## Opportunity Quality
-- [ ] At least 3 opportunity areas identified
-- [ ] Each opportunity has supporting evidence
-- [ ] Opportunities ranked by impact and feasibility
-## Creative Integration
-- [ ] Creative-artifacts/ checked for prior outputs
-- [ ] Prior outputs integrated if available
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/project-brainstorm.md
-- [ ] All required sections present
-- [ ] Recommended next steps included

package/_gaia/lifecycle/workflows/1-analysis/brainstorm-project/instructions.xml

@@ -1,39 +0,0 @@
-<workflow name="brainstorm-project">
-<critical>
-  <mandate>Check creative-artifacts/ for prior brainstorming output before starting</mandate>
-  <mandate>All findings must be grounded in user-provided information</mandate>
-</critical>
-<step n="1" title="Discover Context">
-  <action>Check docs/creative-artifacts/ for prior brainstorming output from creative module</action>
-  <action>If found, load and incorporate insights into the session</action>
-  <action>If not found, note that no prior creative work exists</action>
-</step>
-<step n="2" title="Elicit Project Vision">
-  <ask>What is the business idea or problem you want to explore?</ask>
-  <ask>Who are the target users?</ask>
-  <ask>What pain points does this address?</ask>
-  <ask>What makes this different from existing solutions?</ask>
-</step>
-<step n="3" title="Competitive Landscape">
-  <action>Based on user-provided information, analyze the competitive landscape</action>
-  <action>Note: no web access — use user-provided info and general knowledge only</action>
-  <action>Identify direct and indirect competitors</action>
-  <action>Map competitive positioning</action>
-</step>
-<step n="4" title="Opportunity Synthesis">
-  <action>Synthesize findings into 3-5 opportunity areas</action>
-  <action>For each opportunity: describe it, estimate impact, note evidence</action>
-  <action>Rank opportunities by potential impact and feasibility</action>
-  <action>Collect all ideas explored during the session that did not make the top opportunity list into a "Parking Lot" — for each, note the idea, why it was deprioritized, and under what conditions it might become viable</action>
-</step>
-<step n="5" title="Generate Output">
-  <template-output file="{planning_artifacts}/project-brainstorm.md">
-    Generate structured brainstorm output with: vision summary, target users, pain points, competitive landscape, opportunity areas (ranked), Parking Lot (deprioritized ideas with reasoning and revival conditions), and next steps per lifecycle-sequence.yaml.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-market-research">Conduct market research to validate competitive landscape</primary>
-  <alternative command="/gaia-domain-research" context="If domain-specific research is needed first"/>
-  <alternative command="/gaia-tech-research" context="If technology evaluation is needed first"/>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/1-analysis/brainstorm-project/workflow.yaml

@@ -1,19 +0,0 @@
-name: brainstorm-project
-description: 'Brainstorm a new project idea with structured techniques'
-module: lifecycle
-agent: analyst
-config_resolved: "{installed_path}/.resolved/brainstorm-project.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/1-analysis/brainstorm-project"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  creative_outputs:
-    whole: "{creative_artifacts}/*.md"
-    load_strategy: "INDEX_GUIDED"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/project-brainstorm.md"

package/_gaia/lifecycle/workflows/1-analysis/create-product-brief/checklist.md

@@ -1,27 +0,0 @@
----
-title: 'Product Brief Validation'
-validation-target: 'Product brief'
-required-inputs:
-  - '{planning_artifacts}/project-brainstorm.md'
-validation-rules:
-  - 'All 5 core sections present'
-  - 'Success metrics are measurable'
----
-## Core Sections
-- [ ] Vision statement present and clear
-- [ ] Target users defined with personas
-- [ ] Problem statement articulated
-- [ ] Proposed solution described
-- [ ] Success metrics defined and measurable
-## Input Integration
-- [ ] Brainstorm output checked and incorporated
-- [ ] Market research checked and incorporated
-- [ ] Creative outputs checked and incorporated
-## Quality
-- [ ] Vision aligns with problem statement
-- [ ] Solution addresses identified pain points
-- [ ] Metrics map to stated goals
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/product-brief.md
-- [ ] All required sections complete
-- [ ] Post-complete quality gate passes

package/_gaia/lifecycle/workflows/1-analysis/create-product-brief/instructions.xml

@@ -1,57 +0,0 @@
-<workflow name="create-product-brief">
-<critical>
-  <mandate>Invoke discover-inputs protocol to load upstream artifacts</mandate>
-  <mandate>All sections must be collaboratively developed with the user</mandate>
-</critical>
-<step n="1" title="Discover Inputs">
-  <action>Invoke discover-inputs protocol</action>
-  <action>Load brainstorm output if available</action>
-  <action>Load market research if available</action>
-  <action>Load domain research if available</action>
-  <action>Load technical research if available</action>
-  <action>Load creative outputs if available</action>
-  <action>Summarize what upstream context was found</action>
-</step>
-<step n="2" title="Vision Statement">
-  <action>Collaboratively craft vision statement with user</action>
-  <action>Incorporate insights from prior analysis if available</action>
-  <ask>What is the core vision for this product?</ask>
-</step>
-<step n="3" title="Target Users">
-  <action>Define user personas based on research</action>
-  <action>For each persona: name, role, goals, pain points, context</action>
-</step>
-<step n="4" title="Problem Statement">
-  <action>Articulate the core problem being solved</action>
-  <action>Ground in user research, market findings, and domain landscape</action>
-</step>
-<step n="5" title="Proposed Solution">
-  <action>Define high-level solution approach</action>
-  <action>Key features and differentiators</action>
-  <action>Reference technical research for technology selection rationale if available</action>
-</step>
-<step n="6" title="Scope, Risks and Competitive Landscape">
-  <action>Define what is in-scope for this product and what is explicitly out of scope</action>
-  <action>Document known risks, dependencies, and assumptions the solution depends on</action>
-  <action>Summarize competitive landscape from upstream brainstorm and market research — key competitors, positioning, and differentiation</action>
-</step>
-<step n="7" title="Success Metrics">
-  <action>Define measurable KPIs and success criteria</action>
-  <action>Include both quantitative and qualitative metrics</action>
-</step>
-<step n="8" title="Generate Output">
-  <template-output file="{planning_artifacts}/product-brief.md">
-    Generate product brief with these exact sections:
-    ## Vision Statement — core product vision
-    ## Target Users — user personas (name, role, goals, pain points, context for each)
-    ## Problem Statement — core problem being solved, grounded in research
-    ## Proposed Solution — high-level solution approach
-    ## Key Features — feature list with differentiators
-    ## Scope and Boundaries — what is in-scope and what is explicitly out of scope
-    ## Risks and Assumptions — known risks, dependencies, and assumptions
-    ## Competitive Landscape — summary of competitive positioning from upstream research
-    ## Success Metrics — measurable KPIs and success criteria
-    ## Next Steps — per lifecycle-sequence.yaml
-  </template-output>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/1-analysis/create-product-brief/workflow.yaml

@@ -1,38 +0,0 @@
-name: create-product-brief
-description: 'Create product brief through collaborative discovery'
-module: lifecycle
-agent: analyst
-config_resolved: "{installed_path}/.resolved/create-product-brief.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/1-analysis/create-product-brief"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  brainstorm:
-    whole: "{planning_artifacts}/project-brainstorm.md"
-    load_strategy: "FULL_LOAD"
-  market_research:
-    whole: "{planning_artifacts}/market-research.md"
-    load_strategy: "FULL_LOAD"
-  domain_research:
-    whole: "{planning_artifacts}/domain-research.md"
-    load_strategy: "FULL_LOAD"
-  technical_research:
-    whole: "{planning_artifacts}/technical-research.md"
-    load_strategy: "FULL_LOAD"
-  creative_outputs:
-    whole: "{creative_artifacts}/*.md"
-    load_strategy: "INDEX_GUIDED"
-quality_gates:
-  pre_start:
-    - check: "brainstorm_exists({planning_artifacts}/project-brainstorm.md)"
-      on_fail: "HALT: Brainstorm artifact not found at {planning_artifacts}/project-brainstorm.md. Run /gaia-brainstorm first."
-  post_complete:
-    - check: "product_brief_has_all_sections"
-      on_fail: "HALT: Product brief must include all sections: Vision Statement, Target Users, Problem Statement, Proposed Solution, Key Features, Scope and Boundaries, Risks and Assumptions, Competitive Landscape, Success Metrics. Review {planning_artifacts}/product-brief.md and add missing sections."
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/product-brief.md"

package/_gaia/lifecycle/workflows/1-analysis/domain-research/checklist.md

@@ -1,22 +0,0 @@
----
-title: 'Domain Research Validation'
-validation-target: 'Domain research report'
-validation-rules:
-  - 'Domain clearly defined'
-  - 'Risk assessment included'
----
-## Scope
-- [ ] Domain/industry clearly defined
-- [ ] Focus areas identified
-## Domain Knowledge
-- [ ] Key players identified
-- [ ] Regulatory landscape documented
-- [ ] Industry trends mapped
-- [ ] Terminology glossary included
-## Risk Assessment
-- [ ] Regulatory risks identified
-- [ ] Technical risks assessed
-- [ ] Market risks evaluated
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/domain-research.md
-- [ ] All required sections present

package/_gaia/lifecycle/workflows/1-analysis/domain-research/instructions.xml

@@ -1,34 +0,0 @@
-<workflow name="domain-research">
-<critical>
-  <mandate>Check web access availability before research</mandate>
-  <mandate>Clearly distinguish between verified facts and general knowledge</mandate>
-</critical>
-<step n="1" title="Domain Scoping">
-  <ask>What domain or industry do you want to research?</ask>
-  <ask>Are there specific aspects you want to focus on?</ask>
-</step>
-<step n="2" title="Web Access Check">
-  <action>Check if MCP web tools are available</action>
-  <check if="no_web_access">Notify user and proceed with general knowledge only</check>
-</step>
-<step n="3" title="Domain Landscape">
-  <action>Identify key players and organizations in the domain</action>
-  <action>Document relevant regulations and compliance requirements</action>
-  <action>Map industry trends and emerging patterns</action>
-  <action>Define domain-specific terminology and concepts</action>
-</step>
-<step n="4" title="Domain-Specific Risks">
-  <action>Identify regulatory and compliance risks</action>
-  <action>Assess technical risks specific to the domain</action>
-  <action>Evaluate market and competitive risks</action>
-</step>
-<step n="5" title="Generate Output">
-  <template-output file="{planning_artifacts}/domain-research.md">
-    Generate domain research report with: domain overview, key players, regulatory landscape, trends, terminology glossary, risk assessment, and recommendations.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-tech-research">Evaluate technology options for the project</primary>
-  <alternative command="/gaia-product-brief" context="If all research is complete"/>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/1-analysis/domain-research/workflow.yaml

@@ -1,15 +0,0 @@
-name: domain-research
-description: 'Conduct domain and industry research'
-module: lifecycle
-agent: analyst
-config_resolved: "{installed_path}/.resolved/domain-research.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/1-analysis/domain-research"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/domain-research.md"

package/_gaia/lifecycle/workflows/1-analysis/market-research/checklist.md

@@ -1,28 +0,0 @@
----
-title: 'Market Research Validation'
-validation-target: 'Market research report'
-validation-rules:
-  - 'At least 3 competitors analyzed'
-  - 'TAM/SAM/SOM estimates provided with assumptions'
----
-## Scope
-- [ ] Market/industry clearly defined
-- [ ] Geographic scope stated
-## Competition
-- [ ] At least 3 competitors analyzed
-- [ ] Strengths and weaknesses for each
-- [ ] Competitive positioning matrix included
-## Customers
-- [ ] Target segments defined with evidence
-- [ ] User behavior patterns identified
-- [ ] Underserved needs highlighted
-## Market Sizing
-- [ ] TAM estimate with assumptions
-- [ ] SAM estimate with assumptions
-- [ ] SOM estimate with assumptions
-## Web Access
-- [ ] Web access guard triggered if no access
-- [ ] Limitation noted in output if applicable
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/market-research.md
-- [ ] All required sections present

package/_gaia/lifecycle/workflows/1-analysis/market-research/instructions.xml

@@ -1,42 +0,0 @@
-<workflow name="market-research">
-<critical>
-  <mandate>Check web access availability before proceeding with research</mandate>
-  <mandate>If no web access, proceed with user-provided data and general knowledge only</mandate>
-</critical>
-<step n="1" title="Scope Definition">
-  <ask>What market or industry do you want to research?</ask>
-  <ask>Are there specific competitors you want analyzed?</ask>
-  <ask>What geographic scope? (global, regional, local)</ask>
-</step>
-<step n="2" title="Web Access Check">
-  <action>Check if MCP web tools are available for live research</action>
-  <check if="web_access_available">Proceed with live web research in subsequent steps</check>
-  <check if="no_web_access">Notify user: "Web access unavailable. Proceeding with user-provided data and general knowledge. Results may be less comprehensive."</check>
-</step>
-<step n="3" title="Competitive Analysis">
-  <action>Identify and analyze competitors (direct and indirect)</action>
-  <action>For each competitor: strengths, weaknesses, market position, pricing model</action>
-  <action>Create competitive positioning matrix</action>
-</step>
-<step n="4" title="Customer Research">
-  <action>Define target customer segments</action>
-  <action>Analyze user behavior patterns and needs</action>
-  <action>Identify underserved needs and market gaps</action>
-</step>
-<step n="5" title="Market Sizing">
-  <action>Estimate Total Addressable Market (TAM)</action>
-  <action>Estimate Serviceable Addressable Market (SAM)</action>
-  <action>Estimate Serviceable Obtainable Market (SOM)</action>
-  <action>State all assumptions clearly</action>
-</step>
-<step n="6" title="Generate Output">
-  <template-output file="{planning_artifacts}/market-research.md">
-    Generate market research report with: executive summary, competitive analysis, customer segments, market sizing (TAM/SAM/SOM), key findings, and strategic recommendations.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-domain-research">Research the domain or industry in depth</primary>
-  <alternative command="/gaia-tech-research" context="If technology evaluation is needed"/>
-  <alternative command="/gaia-product-brief" context="If all research is complete"/>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/1-analysis/market-research/workflow.yaml

@@ -1,15 +0,0 @@
-name: market-research
-description: 'Conduct market research on competition and customers'
-module: lifecycle
-agent: analyst
-config_resolved: "{installed_path}/.resolved/market-research.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/1-analysis/market-research"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/market-research.md"