gaia-framework 1.57.0 → 1.57.2

package/_gaia/lifecycle/workflows/anytime/memory-hygiene/instructions.xml

@@ -1,108 +0,0 @@
-<workflow name="memory-hygiene">
-<critical>
-  <mandate>User-initiated cross-sidecar reads are explicitly allowed per agent-specification-protocol</mandate>
-  <mandate>Never modify a sidecar file without explicit user confirmation for each entry</mandate>
-  <mandate>Preserve the sidecar file header and marker comment in all modifications</mandate>
-  <mandate>Process sidecars one at a time — release previous sidecar content before loading next (JIT)</mandate>
-</critical>
-
-<step n="1" title="Scan Sidecars">
-  <action>Read {memory_path}/config.yaml to get sidecar_root path</action>
-  <action>Enumerate all 9 *-sidecar/ directories under {memory_path}/</action>
-  <action>For each directory, read the .md file(s) inside</action>
-  <action>Determine if content exists beyond the template header — look for text after the
-    &lt;!-- Decisions will be appended below this line --&gt; marker or similar comment markers</action>
-  <action>Build two lists:
-    - Sidecars with content (candidates for hygiene review)
-    - Sidecars without content (empty — will be skipped)</action>
-  <check if="zero sidecars have content">Report "All sidecars are empty — nothing to review" and complete the workflow</check>
-  <action>Report to user: "{N} sidecars with content found, {M} empty. Proceeding with review."</action>
-</step>
-
-<step n="2" title="Load Reference Artifacts">
-  <action>Attempt to read each reference artifact (record which exist and which are missing):
-    - {planning_artifacts}/architecture.md — for architect, devops, security sidecar validation
-    - {planning_artifacts}/prd.md — for pm sidecar validation
-    - {planning_artifacts}/infrastructure-design.md — for devops sidecar validation
-    - {test_artifacts}/test-plan.md — for test-architect sidecar validation
-    - {implementation_artifacts}/sprint-status.yaml — for sm sidecar validation</action>
-  <action>For each artifact that exists: retain its key sections and structure for comparison</action>
-  <check if="no reference artifacts exist">Warn user: "No reference artifacts found. Hygiene will be limited to structural checks (orphaned references to nonexistent components). Create architecture.md or prd.md for full cross-referencing."</check>
-</step>
-
-<step n="3" title="Cross-Reference Entries">
-  <action>Process each sidecar with content one at a time (JIT — release previous before loading next)</action>
-  <action>Identify individual entries within the sidecar by:
-    - ### headings (ADR-style entries)
-    - Date-prefixed list items (e.g., "- 2026-03-01: Decided to...")
-    - If format is unstructured: treat entire post-header content as a single entry</action>
-  <action>For each sidecar, apply its specific validation rules:
-    - architect-sidecar: Compare each entry against architecture.md ADR section. Check if the
-      technology, component, or pattern referenced still exists in current architecture.
-    - devops-sidecar: Compare against architecture.md deployment section and infrastructure-design.md.
-      Check for changed hosting, container, or IaC choices.
-    - security-sidecar: Compare against architecture.md security section. Check if referenced
-      components still exist and threat mitigations match current security posture.
-    - pm-sidecar: Compare against prd.md requirements and scope. Check if deprioritized or
-      descoped features still have active product decisions.
-    - sm-sidecar: Compare sprint references against sprint-status.yaml. Check for velocity data
-      referencing completed or nonexistent sprints.
-    - test-architect-sidecar: Compare against test-plan.md strategy and framework choices.
-    - tech-writer-sidecar: Validate referenced conventions against project file patterns.
-    - orchestrator-sidecar: SKIP — session log only, no decisions to validate.
-    - storyteller-sidecar: SKIP — creative log, no decisions to validate.</action>
-  <action>If a sidecar's reference artifact is missing: flag all its entries as "UNVERIFIABLE —
-    reference artifact not found" and note which artifact would be needed</action>
-  <action>For all sidecars: scan each entry for references to specific component names, service names, or artifact filenames. Cross-reference against current artifact content. If a referenced name does not appear in any current artifact, flag as potential ORPHANED or RENAMED. For RENAMED candidates: search for semantically similar names in current artifacts and suggest the likely rename (e.g., "auth-service → identity-service?").</action>
-</step>
-
-<step n="4" title="Classify Entries">
-  <action>Assign each sidecar entry one of four statuses:
-    - ACTIVE: Entry is consistent with current reference artifacts — no action needed
-    - STALE: The referenced artifact has changed since this entry was recorded (e.g.,
-      architecture.md has a newer ADR on the same topic with a different decision)
-    - CONTRADICTED: Current artifact explicitly states the opposite of what this entry records
-      (e.g., sidecar says "Use PostgreSQL", architecture.md says "Use MongoDB" for the same component)
-    - ORPHANED: The component, service, or feature referenced in this entry no longer exists
-      in any current artifact</action>
-  <action>Record evidence for each classification: which artifact section confirms or contradicts,
-    what changed, or what is missing</action>
-</step>
-
-<step n="5" title="Present Findings">
-  <action>Generate a findings report with:
-    - Summary: total entries scanned, counts by status (ACTIVE, STALE, CONTRADICTED, ORPHANED)
-    - Detailed table grouped by sidecar, sorted by severity (CONTRADICTED first, then STALE,
-      then ORPHANED, then ACTIVE):
-
-    | Sidecar | Entry | Status | Evidence | Reference Artifact |
-    |---------|-------|--------|----------|--------------------|
-
-    - Skipped sidecars listed separately (empty or session/creative logs)</action>
-  <template-output file="{implementation_artifacts}/memory-hygiene-report-{date}.md">
-    Memory hygiene report with summary counts, detailed findings table, and skipped sidecars list.
-  </template-output>
-</step>
-
-<step n="6" title="User Action on Flagged Items">
-  <action>For each entry with status other than ACTIVE, ask the user to choose one action:
-    - Keep: Add a [Reviewed: {date}] annotation to the entry — confirms user saw and accepted it
-    - Archive: Move the entry to a ## Archived Decisions section at the bottom of the sidecar file,
-      prefixed with [Archived: {date} — Reason: {status}]. Create the section if it does not exist.
-    - Delete: Remove the entry from the sidecar file entirely</action>
-  <action>When modifying sidecar files:
-    - ALWAYS preserve the file header (title, description, marker comment)
-    - ALWAYS keep the &lt;!-- Decisions will be appended below this line --&gt; marker intact
-    - Place the ## Archived Decisions section after all active entries but before end of file
-    - Active entries remain between the marker comment and the ## Archived Decisions section</action>
-  <action>After all user actions are processed: report summary of changes made to each sidecar file</action>
-</step>
-
-<step n="7" title="Optional: Prune Completed Checkpoints" optional="true">
-  <ask>Would you like to prune old completed checkpoints? (yes / skip)</ask>
-  <action if="yes">Read {checkpoint_path}/completed/ and list all .yaml files with dates</action>
-  <ask if="yes">How many sprints of checkpoints to retain? (default: 2)</ask>
-  <action if="yes">Delete checkpoint files older than the retention window</action>
-  <action if="yes">Report: "Pruned {N} completed checkpoint(s). Retained {M} within the {retention} sprint window."</action>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/anytime/memory-hygiene/workflow.yaml

@@ -1,15 +0,0 @@
-name: memory-hygiene
-description: 'Detect stale, contradicted, or superseded decisions in agent memory sidecars'
-module: lifecycle
-agent: orchestrator
-config_resolved: "{installed_path}/.resolved/memory-hygiene.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/anytime/memory-hygiene"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{implementation_artifacts}/memory-hygiene-report-{date}.md"

package/_gaia/lifecycle/workflows/anytime/performance-review/checklist.md

@@ -1,25 +0,0 @@
----
-title: 'Performance Review Validation'
-validation-target: 'Performance review report'
-required-inputs: []
----
-## Scope
-- [ ] Performance scope defined (endpoints, flows, system)
-- [ ] Frontend vs backend scope clarified
-## Baseline
-- [ ] Current metrics documented or baseline plan established
-- [ ] SLOs identified
-## Load Testing
-- [ ] Test scenarios match real user behavior
-- [ ] Traffic patterns defined
-- [ ] Tooling recommended
-## Bottlenecks
-- [ ] Database access patterns reviewed
-- [ ] Blocking operations identified
-- [ ] Caching strategy evaluated
-## Recommendations
-- [ ] Improvements are specific and prioritized
-- [ ] Each has estimated impact
-- [ ] Categorized by effort level
-## Output Verification
-- [ ] Report file generated at {test_artifacts}/

package/_gaia/lifecycle/workflows/anytime/performance-review/instructions.xml

@@ -1,62 +0,0 @@
-<workflow name="performance-review">
-<critical>
-  <mandate>Story must be in review status before performance review</mandate>
-  <mandate>Auto-pass if no performance-relevant code changes detected</mandate>
-  <mandate>Always measure before recommending optimizations</mandate>
-  <mandate>Report in percentiles (P50, P95, P99), not averages</mandate>
-  <mandate>Output must include machine-readable PASSED or FAILED verdict</mandate>
-  <mandate>When reading or running application source code, use {project-path} as the base directory — NOT {project-root}. {project-path} is resolved by the engine from global.yaml.</mandate>
-</critical>
-<step n="1" title="Load Story">
-  <action>Resolve story file: search for {story_key}-*.md in {implementation_artifacts}/ using glob pattern to match the full filename ({story_key}-{title_slug}.md)</action>
-  <action>Read story file, identify files changed</action>
-  <action>Extract the list of files changed from the story file</action>
-</step>
-<step n="2" title="Status Gate">
-  <action>Verify story is in 'review' status</action>
-  <check if="status != review">HALT: Story must be in review status before performance review</check>
-</step>
-<step n="3" title="Auto-Pass Classification">
-  <action>Classify each changed file as performance-relevant or not:</action>
-  <action>Performance-relevant: files containing DB queries, API endpoints, data processing, rendering logic, loops/algorithms, middleware, caching, network calls</action>
-  <action>Not relevant: markdown (.md), config/yaml/json, test files, static assets, CSS-only, copy/translations, .gitignore, lock files</action>
-  <check if="zero performance-relevant files">
-    Verdict is PASSED with note "No performance-relevant code changes — auto-passed". Skip to step 8 (Generate Output) with this verdict.
-  </check>
-  <action>If ANY performance-relevant files exist: proceed to full review (step 4)</action>
-</step>
-<step n="4" title="N+1 and Database Analysis">
-  <action>Analyze for N+1 queries and inefficient database access patterns</action>
-  <action>Check for missing indexes on queried columns</action>
-  <action>Identify unbounded queries (missing LIMIT, pagination)</action>
-</step>
-<step n="5" title="Memory and Bundle Analysis">
-  <action>Identify memory leaks, large payloads, unoptimized loops</action>
-  <action>Check frontend: bundle size impact, render blocking, unnecessary re-renders</action>
-  <action>Review image optimization and lazy loading</action>
-</step>
-<step n="6" title="Caching and Complexity Review">
-  <action>Review caching strategy: what's cached, what should be, cache invalidation</action>
-  <action>Check for blocking operations and synchronous bottlenecks</action>
-  <action>Analyze algorithm complexity — flag O(n^2) or worse in hot paths</action>
-</step>
-<step n="7" title="Verdict">
-  <action>If NO critical or high severity performance issues: verdict is PASSED</action>
-  <action>If ANY critical or high severity issue found: verdict is FAILED — list blocking findings</action>
-</step>
-<step n="8" title="Generate Output">
-  <template-output file="{implementation_artifacts}/{story_key}-performance-review.md">
-    Generate performance review report with: auto-pass classification result (if applicable), N+1 analysis, memory/bundle findings, caching review, algorithm complexity, and machine-readable verdict (PASSED/FAILED).
-  </template-output>
-</step>
-<step n="9" title="Update Review Gate and Transition">
-  <action>Read story file, locate Review Gate table</action>
-  <action>If PASSED: update Performance Review row status to PASSED, link report file</action>
-  <action>If FAILED: update Performance Review row status to FAILED, link report file. Do NOT change story status — the review-gate-check protocol or run-all-reviews orchestrator handles status transitions.</action>
-  <template-output file="{implementation_artifacts}/{story_key}-*.md">
-    Update story file Review Gate table with performance review result and report link.
-  </template-output>
-  <action>Inform user: "Note: sprint-status.yaml may now be out of sync. Run /gaia-sprint-status to reconcile."</action>
-  <invoke-protocol name="review-gate-check" file="{project-root}/_gaia/core/protocols/review-gate-check.xml" />
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/anytime/performance-review/workflow.yaml

@@ -1,15 +0,0 @@
-name: performance-review
-description: 'Analyze performance bottlenecks and recommend optimizations'
-module: lifecycle
-agent: performance
-config_resolved: "{installed_path}/.resolved/performance-review.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/anytime/performance-review"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{test_artifacts}/performance-review-{date}.md"

package/_gaia/lifecycle/workflows/cross-phase/add-feature/checklist.md

@@ -1,30 +0,0 @@
----
-title: 'Add Feature Validation'
-validation-target: 'Feature Addition Cascade'
----
-## Orchestration
-- [ ] Feature scope captured and confirmed by user
-- [ ] Context flows forward between steps (prd_diff → arch_diff → test_diff → stories)
-- [ ] Steps intelligently skipped when not needed
-## PRD Update
-- [ ] PRD edited with new requirements
-- [ ] New FR/NFR IDs captured for downstream steps
-- [ ] Cascade to architecture classified (NONE/MINOR/SIGNIFICANT)
-## Architecture Update (if applicable)
-- [ ] Architecture edited with changes supporting new requirements
-- [ ] New ADRs recorded
-- [ ] Skipped with justification if cascade_to_arch == NONE
-## Test Plan Update (if applicable)
-- [ ] Test plan edited with new test cases
-- [ ] New test cases map to new FR/NFR IDs
-- [ ] Skipped with justification if no test-plan.md or no new testable behavior
-## Story Creation
-- [ ] New stories created with correct format
-- [ ] Epic assignment confirmed (new or existing)
-- [ ] Story protection enforced (no modification of locked stories)
-## Traceability
-- [ ] Traceability matrix regenerated
-- [ ] New requirements → test cases → stories linked
-## Summary
-- [ ] Final summary presented to user with all artifact statuses
-- [ ] Next steps communicated

package/_gaia/lifecycle/workflows/cross-phase/add-feature/instructions.xml

@@ -1,85 +0,0 @@
-<workflow name="add-feature">
-<critical>
-  <mandate>This is an orchestrator — delegate to sub-workflows via subagents, do not perform edits directly</mandate>
-  <mandate>Context flows forward: PRD diff feeds arch edit, which feeds test plan edit, which feeds story creation</mandate>
-  <mandate>Intelligently skip steps when not needed — do not force all sub-workflows on every feature</mandate>
-</critical>
-
-<step n="1" title="Capture Feature Scope">
-  <ask>Describe the new feature you want to add.</ask>
-  <ask>What is the business driver? (customer request / market opportunity / technical improvement / regulatory)</ask>
-  <ask>Is this linked to a change request? If so, provide the CR ID.</ask>
-  <action>If CR exists: read {planning_artifacts}/change-request-{cr_id}.md for context (impact analysis, approval status)</action>
-  <action>Classify initial scope: how many artifacts will likely need changes?</action>
-  <action>Present scope summary to user for confirmation before proceeding:
-    - Feature: {feature_description}
-    - Driver: {driver}
-    - CR: {cr_id or "none"}
-    - Expected cascade: PRD (always) → Architecture ({likely/unlikely}) → Test Plan ({if exists}) → Stories (always) → Traceability (always)</action>
-</step>
-
-<step n="2" title="Edit PRD">
-  <action>Spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/lifecycle/workflows/2-planning/edit-prd/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY. Context: Adding new feature: {feature_description}. Driver: {driver}. CR ID: {cr_id}. Add new functional and non-functional requirements for this feature. Use CR ID {cr_id} when prompted."</action>
-  <action>When subagent returns: capture the PRD diff — identify NEW requirement IDs (FR-*, NFR-*) added</action>
-  <action>Capture the cascade classification from edit-prd Step 7 (architecture impact: NONE/MINOR/SIGNIFICANT)</action>
-  <action>Store: prd_diff = {new FR/NFR IDs and descriptions}, cascade_to_arch = {NONE/MINOR/SIGNIFICANT}</action>
-</step>
-
-<step n="3" title="Adversarial Review on PRD" optional="true" condition="edit_prd_offered_adversarial">
-  <action>If edit-prd Step 5 ran adversarial review: the subagent already handled it — capture any refined requirements</action>
-  <action>If adversarial findings were incorporated: update prd_diff with refined requirement IDs</action>
-  <action>If adversarial was skipped: proceed to Step 4</action>
-</step>
-
-<step n="4" title="Edit Architecture" optional="true" condition="cascade_to_arch != NONE">
-  <check if="cascade_to_arch == NONE">
-    <action>Inform user: "No architecture changes needed for this feature — PRD changes are requirements-only." Skip to Step 5.</action>
-  </check>
-  <action>Spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/lifecycle/workflows/3-solutioning/edit-architecture/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY. Context: PRD updated with new feature: {feature_description}. New requirements: {prd_diff}. Update architecture to support these requirements. CR ID: {cr_id}."</action>
-  <action>When subagent returns: capture the architecture diff — new ADRs, changed sections, version note</action>
-  <action>Store: arch_diff = {architecture changes made}</action>
-</step>
-
-<step n="5" title="Edit Test Plan" optional="true" condition="test_plan_exists">
-  <check if="test_plan_not_found">
-    <action>Inform user: "No test-plan.md exists. Recommend running /gaia-test-design to create an initial test plan." Skip to Step 6.</action>
-  </check>
-  <ask>Does this feature add new testable behavior? (yes / skip)</ask>
-  <action>If skip: proceed to Step 6.</action>
-  <action>If yes: spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/testing/workflows/edit-test-plan/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY. Context: New feature: {feature_description}. New PRD requirements: {prd_diff}. Architecture changes: {arch_diff}. Add test cases for the new feature."</action>
-  <action>When subagent returns: capture test plan additions (new test case IDs)</action>
-  <action>Store: test_diff = {new test cases added}</action>
-</step>
-
-<step n="6" title="Add Feature Stories">
-  <action>Spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/lifecycle/workflows/4-implementation/add-stories/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY. Context: New feature: {feature_description}. New PRD requirements: {prd_diff}. Architecture changes: {arch_diff}. Create stories for this feature. Determine if a new epic is needed or if stories belong to an existing epic. CR ID: {cr_id}."</action>
-  <action>When subagent returns: capture new story keys and epic assignments</action>
-  <action>Store: new_stories = {list of new story keys created}</action>
-</step>
-
-<step n="7" title="Update Traceability">
-  <action>Spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/testing/workflows/traceability/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY. Regenerate traceability matrix to include new requirements, test cases, and stories."</action>
-  <action>When subagent returns: verify new FR/NFR IDs → test cases → stories are linked</action>
-</step>
-
-<step n="8" title="Readiness Re-check and Summary">
-  <ask>Run readiness check to validate consistency? (yes / skip — recommended for significant features)</ask>
-  <action>If yes: spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/lifecycle/workflows/3-solutioning/implementation-readiness/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY."</action>
-  <action>Present final summary:
-    **Feature Addition Complete: {feature_description}**
-
-    | Artifact | Status | Details |
-    |----------|--------|---------|
-    | PRD | Updated | {new FR/NFR IDs added} |
-    | Architecture | {Updated/Skipped} | {new ADRs or "No changes needed"} |
-    | Test Plan | {Updated/Skipped/Not found} | {new test case IDs or reason} |
-    | Stories | Created | {new story keys} in {epic assignment} |
-    | Traceability | Regenerated | {linkage verified} |
-    | Readiness | {Passed/Skipped} | {status} |
-
-    **Next steps:**
-    - For each new story: run /gaia-create-story {story_key} to elaborate
-    - To start development: run /gaia-sprint-plan or /gaia-correct-course
-  </action>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/cross-phase/add-feature/workflow.yaml

@@ -1,37 +0,0 @@
-name: add-feature
-description: 'Guided orchestrator for adding a new feature — cascades through PRD, architecture, test plan, stories, traceability, and readiness'
-module: lifecycle
-agent: orchestrator
-config_resolved: "{installed_path}/.resolved/add-feature.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/cross-phase/add-feature"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  prd:
-    whole: "{planning_artifacts}/prd.md"
-    load_strategy: "SELECTIVE_LOAD"
-  architecture:
-    whole: "{planning_artifacts}/architecture.md"
-    load_strategy: "SELECTIVE_LOAD"
-  test_plan:
-    whole: "{test_artifacts}/test-plan.md"
-    load_strategy: "SELECTIVE_LOAD"
-  epics:
-    whole: "{planning_artifacts}/epics-and-stories.md"
-    load_strategy: "SELECTIVE_LOAD"
-  sprint_status:
-    whole: "{implementation_artifacts}/sprint-status.yaml"
-    load_strategy: "SELECTIVE_LOAD"
-quality_gates:
-  pre_start:
-    - check: "prd_exists"
-      on_fail: "HALT: prd.md does not exist. Run /gaia-create-prd first."
-    - check: "epics_exists"
-      on_fail: "HALT: epics-and-stories.md does not exist. Run /gaia-create-epics first."
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{planning_artifacts}/epics-and-stories.md"

package/_gaia/lifecycle/workflows/quick-flow/quick-dev/checklist.md

@@ -1,11 +0,0 @@
----
-title: 'Quick Dev Validation'
-validation-target: 'Quick dev implementation'
----
-## Implementation
-- [ ] Spec followed
-- [ ] Tests pass
-- [ ] Acceptance criteria met
-## Checkpoint
-- [ ] WIP checkpoint checked on start
-- [ ] Checkpoint archived on completion

package/_gaia/lifecycle/workflows/quick-flow/quick-dev/instructions.xml

@@ -1,26 +0,0 @@
-<workflow name="quick-dev">
-<critical>
-  <mandate>Check for WIP checkpoint before starting</mandate>
-</critical>
-<step n="1" title="Load Spec">
-  <action>Read quick spec file</action>
-  <action>Check for WIP checkpoint at _memory/checkpoints/quick-dev-{spec_name}.yaml</action>
-</step>
-<step n="2" title="Check WIP">
-  <check if="checkpoint_exists and has files_touched">Validate checksums (shasum -a 256) for each entry in files_touched — flag DELETED or MODIFIED files, offer Proceed / Start fresh / Review before resuming</check>
-  <check if="checkpoint_exists">Offer to resume from last checkpoint or start fresh</check>
-</step>
-<step n="3" title="Implement">
-  <action>Follow spec implementation steps</action>
-  <action>Apply TDD where practical</action>
-  <action>Write checkpoint after each step — include files_touched with path, checksum (shasum -a 256), last_modified (ISO 8601) for all files created/modified</action>
-</step>
-<step n="4" title="Verify">
-  <action>Run tests</action>
-  <action>Validate against spec acceptance criteria</action>
-</step>
-<step n="5" title="Complete">
-  <action>Archive checkpoint to completed/</action>
-  <action>Report implementation complete with files changed</action>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/quick-flow/quick-dev/workflow.yaml

@@ -1,19 +0,0 @@
-name: quick-dev
-description: 'Implement a quick spec'
-module: lifecycle
-agent: dev-*
-config_resolved: "{installed_path}/.resolved/quick-dev.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/quick-flow/quick-dev"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  spec:
-    whole: "{implementation_artifacts}/quick-spec-{{spec_name}}.md"
-    load_strategy: "FULL_LOAD"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "source_code"

package/_gaia/lifecycle/workflows/quick-flow/quick-spec/checklist.md

@@ -1,13 +0,0 @@
----
-title: 'Quick Spec Validation'
-validation-target: 'Quick spec document'
----
-## Scope
-- [ ] Change clearly described
-- [ ] Files identified
-- [ ] Escape hatch offered if scope is large
-## Spec Quality
-- [ ] Implementation steps defined
-- [ ] Acceptance criteria included
-## Output Verification
-- [ ] Quick spec exists at {implementation_artifacts}/quick-spec-{spec_name}.md

package/_gaia/lifecycle/workflows/quick-flow/quick-spec/instructions.xml

@@ -1,27 +0,0 @@
-<workflow name="quick-spec">
-<critical>
-  <mandate>If scope exceeds quick threshold (more than 5 files or 1 day), offer escalation to full lifecycle</mandate>
-</critical>
-<step n="1" title="Scope">
-  <ask>What small change or feature do you want to spec?</ask>
-  <ask>Which files are likely affected?</ask>
-</step>
-<step n="2" title="Quick Analysis">
-  <action>Identify affected files and dependencies</action>
-  <action>Estimate scope: files changed, complexity</action>
-</step>
-<step n="3" title="Escape Hatch Check">
-  <check if="scope_exceeds_quick_threshold">This looks bigger than a quick spec. Would you like to escalate to the full lifecycle? (create-prd → create-architecture → create-epics-stories)</check>
-  <action>If user confirms escalation: suggest /gaia-create-prd</action>
-  <action>If user declines: continue with quick spec</action>
-</step>
-<step n="4" title="Generate Quick Spec">
-  <action>Create lightweight implementation plan</action>
-  <action>Include: what to change, files affected, acceptance criteria, risks</action>
-</step>
-<step n="5" title="Generate Output">
-  <template-output file="{implementation_artifacts}/quick-spec-{spec_name}.md">
-    Generate quick spec with: summary, files to change, implementation steps, acceptance criteria, risks.
-  </template-output>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/quick-flow/quick-spec/workflow.yaml

@@ -1,15 +0,0 @@
-name: quick-spec
-description: 'Create a quick implementation spec for small changes'
-module: lifecycle
-agent: dev-*
-config_resolved: "{installed_path}/.resolved/quick-spec.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/quick-flow/quick-spec"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{implementation_artifacts}/quick-spec-{spec_name}.md"