gaia-framework 1.57.0 → 1.57.2

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

@@ -1,22 +0,0 @@
----
-title: 'Technical Research Validation'
-validation-target: 'Technical research report'
-validation-rules:
-  - 'At least 2 alternatives compared'
-  - 'Trade-off analysis included'
----
-## Scope
-- [ ] Technologies clearly identified
-- [ ] Use case context provided
-- [ ] Constraints documented
-## Evaluation
-- [ ] Maturity assessment for each technology
-- [ ] Community and ecosystem evaluated
-- [ ] Licensing terms noted
-## Trade-offs
-- [ ] Pros/cons matrix included
-- [ ] Alternatives compared across dimensions
-- [ ] Clear recommendation with rationale
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/technical-research.md
-- [ ] All required sections present

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

@@ -1,34 +0,0 @@
-<workflow name="technical-research">
-<critical>
-  <mandate>Check web access availability before research</mandate>
-  <mandate>Provide objective trade-off analysis, not technology advocacy</mandate>
-</critical>
-<step n="1" title="Technology Scoping">
-  <ask>What technologies or tech stack do you want to research?</ask>
-  <ask>What is the use case or problem context?</ask>
-  <ask>Are there constraints (team expertise, budget, timeline)?</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="Technology Evaluation">
-  <action>Assess each technology for: maturity, community size, learning curve, licensing</action>
-  <action>Evaluate ecosystem: libraries, tools, IDE support, documentation quality</action>
-  <action>Check production readiness: stability, performance characteristics, scalability</action>
-</step>
-<step n="4" title="Trade-off Analysis">
-  <action>Create pros/cons matrix for each technology option</action>
-  <action>Compare alternatives across key dimensions</action>
-  <action>Provide recommendation with clear rationale</action>
-</step>
-<step n="5" title="Generate Output">
-  <template-output file="{planning_artifacts}/technical-research.md">
-    Generate technical research report with: technology overview, evaluation matrix, trade-off analysis, recommendation, and migration/adoption considerations.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-product-brief">Consolidate all research into a product brief</primary>
-  <alternative command="/gaia-advanced-elicitation" context="If deeper requirements exploration is needed (optional)"/>
-</next-step>
-</workflow>

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

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

package/_gaia/lifecycle/workflows/2-planning/create-prd/checklist.md

@@ -1,36 +0,0 @@
----
-title: 'PRD Validation'
-validation-target: 'Product Requirements Document'
-required-inputs:
-  - '{planning_artifacts}/product-brief.md'
-validation-rules:
-  - 'All sections present'
-  - 'Each requirement has acceptance criteria'
----
-## Completeness
-- [ ] Overview section present
-- [ ] User personas defined
-- [ ] Functional requirements listed with FR-### IDs
-- [ ] Non-functional requirements defined with NFR-### IDs
-- [ ] User journeys mapped
-- [ ] Data requirements specified
-- [ ] Integration requirements listed
-- [ ] Critical dependencies have failure modes and fallback behavior defined
-- [ ] Out of scope section present
-- [ ] Constraints documented
-- [ ] Success criteria defined
-- [ ] Requirements Summary Table present with all FR and NFR IDs
-## User Focus
-- [ ] Requirements trace to user needs
-- [ ] User stories in standard format
-## Testability
-- [ ] Each requirement has acceptance criteria
-- [ ] Criteria are measurable and unambiguous
-## Prioritization
-- [ ] MoSCoW or equivalent applied to features
-## Consistency
-- [ ] No contradictions between requirements
-- [ ] Terminology used consistently
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/prd.md
-- [ ] All required sections present

package/_gaia/lifecycle/workflows/2-planning/create-prd/instructions.xml

@@ -1,80 +0,0 @@
-<workflow name="create-prd">
-<critical>
-  <mandate>Product brief must exist before starting</mandate>
-  <mandate>Requirements must be discoverable, not guessed</mandate>
-  <mandate>Each requirement must have testable acceptance criteria</mandate>
-  <mandate>Every requirement must have a unique ID: FR-### (functional), NFR-### (non-functional)</mandate>
-</critical>
-<step n="1" title="Load Product Brief">
-  <action>Read {planning_artifacts}/product-brief.md</action>
-  <action>Extract vision, target users, problem statement, proposed solution</action>
-  <action>Extract scope and boundaries, risks and assumptions, competitive landscape, success metrics</action>
-  <check if="{planning_artifacts}/prd.md exists and contains 'Mode: Brownfield'">WARN: A brownfield PRD exists at {planning_artifacts}/prd.md. Continuing will overwrite it. Confirm with user before proceeding.</check>
-</step>
-<step n="2" title="User Interviews">
-  <ask>Who are the primary user types?</ask>
-  <ask>What are their top 3 needs?</ask>
-  <ask>What frustrates them most about current solutions?</ask>
-  <action>Structure responses into user need statements</action>
-</step>
-<step n="3" title="Functional Requirements">
-  <action>List features organized by priority: Must-Have, Should-Have, Nice-to-Have</action>
-  <action>Each feature needs: description, user story format, acceptance criteria</action>
-  <action>Assign unique IDs: FR-001, FR-002, ... — IDs are sequential and never reused</action>
-  <action>Cross-reference with product brief: verify each FR is traceable to the brief's proposed solution or key features. Flag any FR that introduces scope not present in the brief — confirm with user before including.</action>
-</step>
-<step n="4" title="Non-Functional Requirements">
-  <action>Define: performance targets, security requirements, accessibility standards</action>
-  <action>Define: scalability needs, reliability targets, compliance requirements</action>
-  <action>Assign unique IDs: NFR-001, NFR-002, ... — IDs are sequential and never reused</action>
-  <action>Each NFR MUST include a measurable target with a specific threshold (e.g., "response time &lt; 200ms at p95", "99.9% uptime", "WCAG 2.1 AA compliance", "support 10,000 concurrent users"). Reject vague qualifiers like "fast", "secure", "scalable", or "highly available" without numeric criteria.</action>
-</step>
-<step n="5" title="User Journeys">
-  <action>Map key user flows with happy path and error paths</action>
-  <action>Include: entry point, steps, decision points, exit conditions</action>
-</step>
-<step n="6" title="Data Requirements">
-  <action>Identify data stored, processed, and exchanged</action>
-  <action>Define data retention, privacy, and security policies</action>
-</step>
-<step n="7" title="Integration Requirements">
-  <action>List external systems, APIs, and third-party services</action>
-  <action>Define integration patterns and data exchange formats</action>
-  <action>For each critical dependency: define failure mode, fallback behavior, and SLA expectations</action>
-</step>
-<step n="8" title="Out of Scope">
-  <action>List features, integrations, and use cases explicitly excluded from this release</action>
-  <action>For each exclusion: state what is excluded and why (deferred, not needed, separate product)</action>
-  <action>Cross-reference with product brief: items listed as out-of-scope in the brief's "Scope and Boundaries" section must appear here. Flag any brief out-of-scope item missing from this list.</action>
-</step>
-<step n="9" title="Constraints and Assumptions">
-  <action>Document technical, budget, timeline, and team constraints</action>
-  <action>List all assumptions that requirements depend on</action>
-  <action>Cross-reference with product brief: carry forward every risk and assumption from the brief's "Risks and Assumptions" section. Each must appear in this section or be explicitly noted as resolved with justification.</action>
-</step>
-<step n="10" title="Success Criteria">
-  <action>Define measurable acceptance criteria for each feature</action>
-  <action>Define overall product success metrics</action>
-  <action>Cross-reference with product brief: every metric from the brief's "Success Metrics" section must have a corresponding measurable criterion in the PRD. Flag any brief metric not covered.</action>
-</step>
-<step n="11" title="Generate Output">
-  <template-output file="{planning_artifacts}/prd.md">
-    Generate PRD with all sections: overview, user personas, functional requirements (prioritized with FR-### IDs), non-functional requirements (with NFR-### IDs), user journeys, data requirements, integrations, out of scope, constraints, assumptions, success criteria. Include a Requirements Summary Table listing all FR and NFR IDs with their description, priority, and status.
-  </template-output>
-</step>
-<step n="12" title="Adversarial Review">
-  <action>Spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/tasks/review-adversarial.xml. Read its entire contents. Target: {planning_artifacts}/prd.md. Target label: prd. Follow the task instructions EXACTLY." This is required — findings will be incorporated back into the PRD.</action>
-  <action>When subagent returns: verify adversarial-review-prd-{date}.md exists in {planning_artifacts}/</action>
-</step>
-<step n="13" title="Incorporate Adversarial Findings">
-  <action>Read {planning_artifacts}/adversarial-review-prd-{date}.md — extract critical and high severity findings</action>
-  <action>For each critical/high finding: add as a new requirement or refine an existing requirement in the PRD</action>
-  <action>Add a "## Review Findings Incorporated" section to the PRD listing each finding, its severity, and how it was addressed (new requirement added / existing requirement refined / acknowledged as risk)</action>
-  <template-output file="{planning_artifacts}/prd.md">
-    Update the PRD with adversarial review findings incorporated. Critical/high findings become new requirements or refine existing ones. Add "Review Findings Incorporated" section.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-validate-prd">Validate the PRD against quality standards before proceeding</primary>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/2-planning/create-prd/workflow.yaml

@@ -1,23 +0,0 @@
-name: create-prd
-description: 'Create a Product Requirements Document from scratch'
-module: lifecycle
-agent: pm
-config_resolved: "{installed_path}/.resolved/create-prd.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/2-planning/create-prd"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  product_brief:
-    whole: "{planning_artifacts}/product-brief.md"
-    load_strategy: "FULL_LOAD"
-quality_gates:
-  pre_start:
-    - check: "product_brief_exists"
-      on_fail: "HALT: Run /gaia-product-brief first — product brief required before PRD"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/prd.md"

package/_gaia/lifecycle/workflows/2-planning/create-ux-design/checklist.md

@@ -1,26 +0,0 @@
----
-title: 'UX Design Validation'
-validation-target: 'UX design document'
-required-inputs:
-  - '{planning_artifacts}/prd.md'
----
-## User Research
-- [ ] Personas refined with scenarios
-- [ ] Personas trace to PRD user definitions
-## Information Architecture
-- [ ] Sitemap defined
-- [ ] Navigation structure clear
-## Wireframes
-- [ ] Key screens described
-- [ ] Layout and component placement defined
-## Interaction Patterns
-- [ ] Common UI patterns documented
-- [ ] Form behaviors specified
-- [ ] Error states defined
-## Accessibility
-- [ ] WCAG compliance target stated
-- [ ] Keyboard navigation planned
-- [ ] Screen reader support addressed
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/ux-design.md
-- [ ] All required sections present

package/_gaia/lifecycle/workflows/2-planning/create-ux-design/instructions.xml

@@ -1,49 +0,0 @@
-<workflow name="create-ux-design">
-<critical>
-  <mandate>PRD must exist before starting UX design</mandate>
-  <mandate>Every design decision must trace to a user need from the PRD</mandate>
-</critical>
-<step n="1" title="Load PRD">
-  <action>Read {planning_artifacts}/prd.md</action>
-  <action>Extract user personas, user journeys, and functional requirements</action>
-</step>
-<step n="2" title="User Personas">
-  <action>Refine persona definitions from PRD</action>
-  <action>Add: scenarios, goals, tech proficiency, accessibility needs</action>
-</step>
-<step n="3" title="Information Architecture">
-  <action>Design sitemap and navigation structure</action>
-  <action>Define content hierarchy and page relationships</action>
-  <action>Map each page or section to the FR IDs it serves — every page must trace to at least one FR. Flag any user-facing FR from the PRD that has no corresponding page in the sitemap.</action>
-</step>
-<step n="4" title="Wireframes">
-  <action>Create text-based wireframe descriptions for key screens</action>
-  <action>Define layout, component placement, interaction patterns</action>
-  <action>Annotate each wireframe with the FR IDs it addresses. Flag any FR with user-facing behavior that has no wireframe representation.</action>
-</step>
-<step n="5" title="Interaction Patterns">
-  <action>Define common UI patterns used across the application</action>
-  <action>Specify component library or design system choices</action>
-  <action>Document form behaviors, validation, error states</action>
-  <action>Map each interaction flow to the corresponding user journey from the PRD. Every PRD user journey must have a defined interaction pattern.</action>
-</step>
-<step n="6" title="Accessibility">
-  <action>Define WCAG compliance targets (A, AA, AAA)</action>
-  <action>Plan keyboard navigation, screen reader support</action>
-  <action>Define color contrast and text sizing standards</action>
-</step>
-<step n="7" title="Generate Output">
-  <template-output file="{planning_artifacts}/ux-design.md">
-    Generate UX design document with: personas, information architecture, wireframe descriptions, interaction patterns, component specifications, accessibility plan, and FR-to-Screen Mapping table (FR ID | Screen/Page | Wireframe Section).
-  </template-output>
-</step>
-<step n="8" title="Optional: Accessibility Review">
-  <ask>Would you like to review the UX design for WCAG 2.1 accessibility compliance? This spawns a subagent in a separate context. Recommended for user-facing applications. (yes / skip)</ask>
-  <action>If yes: spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/tasks/review-accessibility.xml. Read its entire contents. Target: {planning_artifacts}/ux-design.md. Follow the flow steps EXACTLY. Generate accessibility findings report."</action>
-  <action>If skip: accessibility review can be run anytime later with /gaia-review-a11y</action>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <primary command="/gaia-review-a11y">Review UX design for WCAG 2.1 accessibility compliance</primary>
-  <alternative command="/gaia-create-arch" context="If accessibility review will be done later"/>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/2-planning/create-ux-design/workflow.yaml

@@ -1,23 +0,0 @@
-name: create-ux-design
-description: 'Plan UX patterns and design specifications'
-module: lifecycle
-agent: ux-designer
-config_resolved: "{installed_path}/.resolved/create-ux-design.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/2-planning/create-ux-design"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  prd:
-    whole: "{planning_artifacts}/prd.md"
-    load_strategy: "FULL_LOAD"
-quality_gates:
-  pre_start:
-    - check: "prd_exists"
-      on_fail: "HALT: Run /gaia-create-prd first — PRD required before UX design"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/ux-design.md"

package/_gaia/lifecycle/workflows/2-planning/edit-prd/checklist.md

@@ -1,17 +0,0 @@
----
-title: 'PRD Edit Validation'
-validation-target: 'Edited PRD'
----
-## Edit Quality
-- [ ] Requested changes applied correctly
-- [ ] Unchanged sections preserved
-- [ ] Version note added with date, reason, and CR ID (if applicable)
-- [ ] Consistency maintained across sections
-## Review Gate
-- [ ] Adversarial review completed OR explicitly skipped for minor edits
-- [ ] "Review Findings Incorporated" section updated
-## Cascade Assessment
-- [ ] Architecture impact assessed (NONE/MINOR/SIGNIFICANT)
-- [ ] Next steps communicated to user
-## Output Verification
-- [ ] Output file saved to {planning_artifacts}/prd.md

package/_gaia/lifecycle/workflows/2-planning/edit-prd/instructions.xml

@@ -1,50 +0,0 @@
-<workflow name="edit-prd">
-<critical>
-  <mandate>Preserve existing content not being changed</mandate>
-  <mandate>Add version note documenting what changed and why</mandate>
-  <mandate>Update "Review Findings Incorporated" section after adversarial review</mandate>
-</critical>
-<step n="1" title="Load PRD">
-  <action>Read current {planning_artifacts}/prd.md</action>
-  <action>Display current structure summary to user</action>
-</step>
-<step n="2" title="Identify Changes">
-  <ask>What sections need to change?</ask>
-  <ask>Why are these changes needed?</ask>
-  <ask>Is this linked to a change request? If so, provide the CR ID.</ask>
-  <action>Confirm scope of changes before proceeding</action>
-</step>
-<step n="3" title="Apply Edits">
-  <action>Make requested changes while preserving unchanged content</action>
-  <action>Validate consistency with remaining sections</action>
-  <action>Add version note at top: date, changes made, reason, CR ID (if applicable)</action>
-</step>
-<step n="4" title="Save Updated PRD">
-  <template-output file="{planning_artifacts}/prd.md">
-    Save updated PRD with version note prepended
-  </template-output>
-</step>
-<step n="5" title="Adversarial Review">
-  <ask>The PRD has been updated. Would you like to run an adversarial review? This spawns a subagent in a separate context — recommended for significant changes. (yes / skip for minor edits)</ask>
-  <action>If yes: spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/tasks/review-adversarial.xml. Read its entire contents. Target: {planning_artifacts}/prd.md. Target label: prd. Follow the task instructions EXACTLY."</action>
-  <action>If skip: proceed to step 7 — mark "Review Findings Incorporated" as "Incremental edit — adversarial review skipped (minor change)"</action>
-  <action>If ok: wait for user to confirm adversarial-review-prd-{date}.md exists</action>
-</step>
-<step n="6" title="Incorporate Review Findings" optional="true" condition="adversarial_completed">
-  <action>Read {planning_artifacts}/adversarial-review-prd-{date}.md — extract critical and high severity findings</action>
-  <action>For each critical/high finding: add or refine requirement in the PRD</action>
-  <action>Update the "## Review Findings Incorporated" section — append new entries with amendment date</action>
-  <template-output file="{planning_artifacts}/prd.md">
-    Update the PRD with adversarial review findings incorporated. Append to existing "Review Findings Incorporated" section with amendment date.
-  </template-output>
-</step>
-<step n="7" title="Architecture Cascade Check">
-  <action>Read {planning_artifacts}/architecture.md section headers</action>
-  <action>Compare PRD changes against architecture scope</action>
-  <action>Classify cascade impact:</action>
-  <action>  NONE: requirements-only changes — architecture unaffected</action>
-  <action>  MINOR: architecture needs a section update — recommend /gaia-edit-arch</action>
-  <action>  SIGNIFICANT: new component/API/data model — recommend /gaia-edit-arch with adversarial review, then /gaia-add-stories</action>
-  <action>Report cascade assessment to user with recommended next command(s)</action>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/2-planning/edit-prd/workflow.yaml

@@ -1,22 +0,0 @@
-name: edit-prd
-description: 'Edit an existing PRD'
-module: lifecycle
-agent: pm
-config_resolved: "{installed_path}/.resolved/edit-prd.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/2-planning/edit-prd"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  prd:
-    whole: "{planning_artifacts}/prd.md"
-    load_strategy: "FULL_LOAD"
-  architecture:
-    whole: "{planning_artifacts}/architecture.md"
-    load_strategy: "SELECTIVE_LOAD"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/prd.md"

package/_gaia/lifecycle/workflows/2-planning/validate-prd/checklist.md

@@ -1,12 +0,0 @@
----
-title: 'PRD Validation Report Check'
-validation-target: 'PRD validation report'
----
-## Report Quality
-- [ ] Machine-readable YAML frontmatter present
-- [ ] PASS/FAIL status clearly stated
-- [ ] All findings categorized by severity
-- [ ] Each finding references specific section
-- [ ] Recommendations provided for each finding
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/prd-validation.md

package/_gaia/lifecycle/workflows/2-planning/validate-prd/instructions.xml

@@ -1,52 +0,0 @@
-<workflow name="validate-prd">
-<critical>
-  <mandate>Output must include machine-readable PASS/FAIL status in YAML frontmatter</mandate>
-  <mandate>Report ALL findings, not just the first failure</mandate>
-</critical>
-<step n="1" title="Load PRD">
-  <action>Read {planning_artifacts}/prd.md</action>
-  <action>Parse all sections and requirements</action>
-</step>
-<step n="2" title="Completeness Check">
-  <action>Verify all required sections exist: overview, personas, functional reqs, NFRs, user journeys, data, integrations, constraints, success criteria</action>
-  <action>Flag any missing sections as critical findings</action>
-</step>
-<step n="3" title="Structural Validation">
-  <action>Verify all functional requirements are numbered sequentially (FR-001, FR-002, ...)</action>
-  <action>Verify all non-functional requirements are numbered sequentially (NFR-001, NFR-002, ...)</action>
-  <action>For each FR: verify acceptance criteria exist and are specific (not blank or generic)</action>
-  <action>For each NFR: verify a measurable target exists (e.g., "response time &lt; 200ms" not "fast response")</action>
-  <action>Verify every requirement has a priority assigned (P0/P1/P2/P3 or Must/Should/Could/Won't)</action>
-  <action>Verify user personas referenced in requirements match personas defined in the personas section</action>
-  <action>Flag any structural gaps as critical findings</action>
-</step>
-<step n="4" title="Quality Check">
-  <action>For each requirement verify: testable, unambiguous, prioritized</action>
-  <action>Check acceptance criteria are measurable</action>
-  <action>Flag vague requirements (e.g., "fast", "easy to use" without quantification)</action>
-</step>
-<step n="5" title="Consistency Check">
-  <action>Cross-reference all sections for contradictions</action>
-  <action>Verify terminology is used consistently</action>
-  <action>Check that priorities don't conflict</action>
-</step>
-<step n="6" title="Generate Validation Report">
-  <template-output file="{planning_artifacts}/prd-validation.md">
-    Generate validation report with YAML frontmatter containing machine-readable status:
-    ---
-    status: PASS or FAIL
-    critical_issues: (count)
-    warnings: (count)
-    findings:
-      - severity: critical/warning/info
-        section: "(section name)"
-        issue: "(description)"
-    ---
-    Then detailed findings with recommendations.
-  </template-output>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <on-pass command="/gaia-create-ux">Create UX design specifications</on-pass>
-  <on-fail command="/gaia-edit-prd">Edit the PRD to address validation findings</on-fail>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/2-planning/validate-prd/workflow.yaml

@@ -1,19 +0,0 @@
-name: validate-prd
-description: 'Validate a PRD against standards'
-module: lifecycle
-agent: pm
-config_resolved: "{installed_path}/.resolved/validate-prd.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/2-planning/validate-prd"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  prd:
-    whole: "{planning_artifacts}/prd.md"
-    load_strategy: "FULL_LOAD"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/prd-validation.md"

package/_gaia/lifecycle/workflows/3-solutioning/create-architecture/checklist.md

@@ -1,32 +0,0 @@
----
-title: 'Architecture Validation'
-validation-target: 'Architecture document'
-required-inputs:
-  - '{planning_artifacts}/prd.md'
----
-## Technology
-- [ ] Stack selected with rationale
-- [ ] Trade-offs documented
-## System Design
-- [ ] Component diagram described
-- [ ] Service boundaries defined
-- [ ] Communication patterns specified
-## Data
-- [ ] Data model defined
-- [ ] Data flow documented
-## API
-- [ ] Endpoints overviewed
-- [ ] Auth strategy defined
-## Infrastructure
-- [ ] Deployment topology described
-- [ ] Environments defined
-## ADRs
-- [ ] Decisions recorded in architect-sidecar
-- [ ] Each ADR has context, decision, consequences
-## Gates
-- [ ] PRD has "Review Findings Incorporated" section (hard gate — required before architecture)
-## Adversarial Review
-- [ ] Adversarial review completed on architecture document
-- [ ] Architecture has "Review Findings Incorporated" section
-## Output Verification
-- [ ] Output file exists at {planning_artifacts}/architecture.md