Christian Nennemann
52d9d8dd05
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
31 lines
1.1 KiB
YAML
31 lines
1.1 KiB
YAML
# 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
|