feat: add 4 template bundles (writing, backend, security, quick-fix)

Ready-to-use project templates with team, workflow, domain, and config:
- writing-short-story: fiction 5-15k words, custom archetypes, sonnet for prose
- backend-feature: standard PDCA, full team, haiku for reviews
- security-review: thorough 3-cycle, all reviewers incl. trickster
- quick-fix: minimal 1-cycle, creator+maker+guardian only

templates/bundles/quick-fix/config.yaml

@@ -0,0 +1,18 @@
+# Config: quick-fix defaults
+# Minimal budget, haiku everywhere. Quick fixes should be cheap and fast.
+# If the fix escalates (A1 rule), budget may need manual increase.
+
+budget:
+  max_usd: 2              # Tight budget — this is a small fix
+  warn_at_pct: 80
+
+models:
+  default: haiku           # Haiku for everything — speed over depth
+  creator: haiku
+  maker: haiku
+  guardian: haiku
+
+variables:
+  max_cycles: 1
+  test_command: ""
+  lint_command: ""

templates/bundles/quick-fix/domain.yaml

@@ -0,0 +1,51 @@
+# Domain: Code
+# Standard code domain for quick fixes. Identical to the default code domain.
+# Included for bundle completeness — all bundles ship their own domain config.
+
+name: code
+description: "Software development — bug fixes and patches"
+
+concepts:
+  implementation: "code changes"
+  tests: "automated tests"
+  files_changed: "files changed"
+  test_coverage: "test coverage %"
+  code_review: "code review"
+  build: "build/compile"
+  deploy: "deploy"
+  refactor: "refactor"
+  bug: "bug"
+  feature: "feature"
+  PR: "pull request"
+
+metrics:
+  - files_changed
+  - lines_added
+  - lines_removed
+  - tests_added
+  - tests_passing
+  - coverage_delta
+
+review_focus:
+  guardian:
+    - regression_risk
+    - security_vulnerabilities
+    - breaking_changes
+    - error_handling
+
+context:
+  always:
+    - "README.md"
+    - ".archeflow/config.yaml"
+  plan_phase:
+    - "bug report / description"
+    - "relevant source files"
+    - "existing tests for affected area"
+  do_phase:
+    - "Creator's fix proposal"
+  check_phase:
+    - "git diff from Maker"
+    - "fix proposal risk section"
+
+# All haiku — quick fixes don't need expensive models
+model_overrides: {}

templates/bundles/quick-fix/manifest.yaml

@@ -0,0 +1,19 @@
+# Bundle: quick-fix
+# Minimal setup for small bug fixes and patches. Fast workflow with 1 cycle,
+# reduced team (no Explorer or Sage), and low budget. Get in, fix, get out.
+
+name: quick-fix
+description: "Small bug fix or patch — minimal team, 1 fast cycle, low overhead"
+version: "1.0.0"
+domain: code
+includes:
+  team: team.yaml
+  workflow: workflow.yaml
+  domain: domain.yaml
+  config: config.yaml
+  archetypes: []
+requires: []
+variables:
+  max_cycles: 1            # Fast: single cycle, ship it
+  test_command: ""         # Override: pytest, cargo test, npm test, etc.
+  lint_command: ""         # Override: ruff, clippy, eslint, etc.

templates/bundles/quick-fix/team.yaml

@@ -0,0 +1,30 @@
+# Team: Quick Fix
+# Minimal team for small bug fixes. No Explorer (scope is known),
+# no Sage (quality review is overkill for a patch). Creator designs the fix,
+# Maker applies it, Guardian sanity-checks for regressions.
+
+name: quick-fix
+description: "Minimal team for small fixes: design, implement, sanity-check"
+domain: code
+
+# Plan: creator only — scope is already known for a bug fix.
+#        Creator identifies root cause and designs the fix.
+plan: [creator]
+
+# Do: maker applies the fix and runs tests.
+do: [maker]
+
+# Check: guardian only — checks for regressions, security issues, breaking changes.
+#         No Sage/Skeptic/Trickster — keep overhead minimal.
+check: [guardian]
+
+exit: all_approved
+max_cycles: ${max_cycles}
+
+# Notes:
+# - If Guardian finds 2+ CRITICALs, orchestration rule A1 escalates to standard
+#   workflow automatically (adds Sage + Skeptic for next cycle)
+# - For truly trivial fixes (typo, config change), even this may be overkill —
+#   but it ensures at least one review pass happens
+# - If the fix turns out to be more complex than expected, abort and use
+#   backend-feature bundle instead

templates/bundles/quick-fix/workflow.yaml

@@ -0,0 +1,66 @@
+# Workflow: Quick Fix
+# Fast PDCA for small bug fixes. 1 cycle, minimal team.
+# If the fix is clean, ships in a single pass.
+# If Guardian escalates (A1 rule), second cycle adds more reviewers automatically.
+
+name: quick-fix
+description: "Fast bug fix — 1 cycle, creator + maker + guardian"
+team: quick-fix
+
+phases:
+  plan:
+    archetypes: [creator]
+    parallel: false
+    description: |
+      Creator identifies root cause and designs the fix:
+      - What is the bug? (reproduce or confirm from description)
+      - Where is the root cause? (file, function, line)
+      - What is the fix? (specific change, not a rewrite)
+      - What could break? (regression risk assessment)
+      - What test proves it's fixed?
+      Keep it brief — this is a patch, not a feature.
+    inputs:
+      - "Bug report / description"
+      - "Relevant source files"
+      - "Existing tests for affected area"
+
+  do:
+    archetypes: [maker]
+    parallel: false
+    description: |
+      Apply the fix. Keep changes minimal and focused.
+      1. Make the code change
+      2. Add or update test that reproduces the bug and verifies the fix
+      3. Run tests (${test_command}) — all must pass
+      4. Run lint (${lint_command}) — no new warnings
+      5. Single commit with descriptive message
+    inputs:
+      - "Creator's fix proposal"
+      - "Affected source files"
+
+  check:
+    archetypes: [guardian]
+    parallel: false
+    description: |
+      Guardian sanity-checks the fix:
+      - Does the fix address the root cause (not just the symptom)?
+      - Are there regressions? (check test coverage of changed code)
+      - Any security implications?
+      - Any breaking changes to public API?
+      If clean: APPROVED. If 2+ CRITICALs: A1 escalation kicks in automatically.
+    inputs:
+      - "git diff from Maker"
+      - "Creator's fix proposal (regression risk section)"
+
+  act:
+    exit_when: all_approved
+    max_cycles: ${max_cycles}
+    on_reject: |
+      Guardian rejection: fix the specific issue and re-run tests.
+      If the fix is growing in scope, consider switching to backend-feature bundle.
+      A1 escalation (2+ CRITICALs) adds Sage + Skeptic — accept the cost.
+
+hooks:
+  pre_plan: []
+  post_check: []
+  post_act: []