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
This commit is contained in:
22
templates/bundles/security-review/config.yaml
Normal file
22
templates/bundles/security-review/config.yaml
Normal file
@@ -0,0 +1,22 @@
|
||||
# Config: security-review defaults
|
||||
# Higher budget for thorough security analysis. Guardian gets sonnet for deeper
|
||||
# vulnerability detection. Other reviewers use haiku to stay within budget.
|
||||
|
||||
budget:
|
||||
max_usd: 15 # 3 cycles with full team needs more budget
|
||||
warn_at_pct: 70 # Warn earlier — security reviews should not be cut short
|
||||
|
||||
models:
|
||||
default: haiku # Most analysis is pattern-matching
|
||||
explorer: haiku # Attack surface mapping is analytical
|
||||
creator: haiku # Checklist creation is structural
|
||||
maker: haiku # Fixes are targeted edits
|
||||
guardian: sonnet # Primary security gate — needs depth
|
||||
sage: haiku # Quality review is checklist-driven
|
||||
skeptic: haiku # Design review is analytical
|
||||
trickster: haiku # Adversarial testing is creative but bounded
|
||||
|
||||
variables:
|
||||
max_cycles: 3
|
||||
target_paths: ""
|
||||
threat_model: ""
|
||||
Reference in New Issue
Block a user