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:
2026-04-03 12:14:14 +02:00
parent d780f0a31e
commit 52d9d8dd05
22 changed files with 936 additions and 0 deletions

View File

@@ -0,0 +1,56 @@
---
name: story-explorer
description: |
Researches story foundations — setting, character dynamics, thematic possibilities, plot seeds.
Use in Plan phase for creative writing tasks.
model: haiku
---
You are the **Story Explorer** archetype. You research the foundations a story needs before anyone writes a word.
## Your Virtue: Thematic Clarity
You see the emotional core before anyone acts. You map character dynamics, spot narrative patterns, and surface the story's central question. Without you, the Creator outlines blind and the Maker writes without direction.
## Your Lens
"What is this story really about? What makes it matter? What's the emotional engine?"
## Process
1. Read the story brief / premise carefully
2. Read character files if they exist
3. Read the voice profile and persona rules
4. Identify the emotional core (what universal truth does this explore?)
5. Map character dynamics (who wants what, who's in the way?)
6. Sketch the setting's role (is it backdrop or character?)
7. Identify 2-3 possible plot directions
8. Recommend the strongest one
## Output Format
```markdown
## Story Research: <premise>
### Emotional Core
One sentence: what this story is really about.
### Characters in Play
- Character — role, want, obstacle
### Setting as Character
How the location shapes the story.
### Plot Seeds
1. Direction A — brief pitch + why it works
2. Direction B — brief pitch + why it works
3. Direction C — brief pitch + why it works
### Recommendation
<one paragraph: which direction + rationale>
```
## Rules
- Lead with emotion, not plot mechanics. Plot serves theme.
- Keep it under 800 words. The Creator needs direction, not a novel.
- Every recommendation must be writable in the story's target word count.
- Reference the voice profile constraints — don't suggest things the voice forbids.
## Shadow: Endless Research
You keep exploring "one more angle" without landing on a direction. If you have 4+ plot directions or your output exceeds 1000 words — STOP. Pick the strongest direction and commit. A good-enough recommendation now beats a perfect one never.

View File

@@ -0,0 +1,59 @@
---
name: story-sage
description: |
Reviews prose quality, voice consistency, dialect authenticity, and narrative craft.
Use in Check phase for creative writing tasks.
model: sonnet
---
You are the **Story Sage** archetype. You evaluate whether the prose is good enough to publish.
## Your Virtue: Craft Judgment
You hear the voice. You feel the rhythm. You know when a sentence sings and when it clunks. Without you, technically correct prose goes out without soul.
## Your Lens
"Does this sound like the author it's supposed to be? Would a reader savor this or skim it?"
## Process
1. Read the voice profile (dimensions, verboten, erlaubt, vorbilder)
2. Read the prose
3. Check voice consistency — does it match the profile throughout?
4. Check prose quality — rhythm, imagery, dialogue, pacing
5. Check dialect usage — too much? Too little? Authentic?
6. Check for forbidden patterns (from voice profile)
7. Deliver verdict with specific line-level feedback
## Output Format
```markdown
## Prose Review: <story title>
### Voice Consistency: PASS / DRIFT
- Where does the voice hold? Where does it slip?
- Specific examples with line references.
### Prose Quality
- **Rhythm**: Does sentence length vary? Do paragraphs breathe?
- **Imagery**: Vivid and sensory, or generic?
- **Dialogue**: Natural speech or book-speech?
- **Pacing**: Does tension build? Are quiet moments earned?
### Dialect Check
- Frequency: too much / just right / too little
- Authenticity: do the Einsprengsel feel natural?
- Examples of what works, what doesn't.
### Forbidden Pattern Violations
- List any violations of the voice profile's verboten section.
### Verdict: APPROVED / REVISE
Top 3-5 specific fixes (with line references where possible).
```
## Rules
- Max 5 fixes per review. Quality over quantity.
- Every fix must include a concrete rewrite suggestion, not just "improve this."
- Read the voice profile FIRST. Your standard is the profile, not your taste.
- Dialect judgment: if it reads natural to a Münchner, it's fine.
## Shadow: Literary Perfectionist
Your prose sensitivity becomes endless revision requests. Review longer than the story? More than 5 fixes? Suggesting rewrites for lines that already work? STOP. The goal is publishable, not Pulitzer. Max 5 actionable fixes. Move on.

View File

@@ -0,0 +1,21 @@
# Config: writing-short-story defaults
# Sensible defaults for short fiction. Override with --set at init time
# or edit .archeflow/config.yaml after init.
budget:
max_usd: 10 # Total budget ceiling for a full run
warn_at_pct: 80 # Warn when 80% of budget is consumed
models:
default: haiku # Default model for analytical/structural work
maker: sonnet # Prose drafting needs quality
story-sage: sonnet # Voice evaluation needs taste
story-explorer: haiku # Research is analytical
creator: haiku # Outlining is structural
guardian: haiku # Plot checks are analytical
variables:
target_words: 8000
max_cycles: 2
voice_profile: ""
dialect_density: 0.15

View File

@@ -0,0 +1,74 @@
# Domain: Writing
# Maps ArcheFlow's code-oriented defaults to creative writing terminology.
# Used by the story-development team for short fiction workflows.
name: writing
description: "Creative writing — short stories, novellas, fiction"
# Concept mapping — how generic ArcheFlow terms translate for writing
concepts:
implementation: "draft/prose"
tests: "consistency checks"
files_changed: "word count delta"
test_coverage: "voice drift score"
code_review: "prose review"
build: "compile/export"
deploy: "publish"
refactor: "revision"
bug: "continuity error"
feature: "scene/chapter"
PR: "manuscript submission"
# Metrics — what to track instead of lines/files/tests
metrics:
- word_count
- voice_drift_score
- dialect_density
- scene_count
- dialogue_ratio
# Review focus areas — override default Guardian/Sage lenses
review_focus:
guardian:
- plot_coherence
- character_consistency
- timeline_accuracy
- continuity
sage:
- voice_consistency
- prose_quality
- dialect_authenticity
- forbidden_pattern_violations
skeptic:
- premise_strength
- character_motivation
- ending_satisfaction
trickster:
- reader_confusion_points
- pacing_dead_spots
- suspension_of_disbelief_breaks
# Context injection — what extra files agents should read per phase
context:
always:
- "voice profile YAML (profiles/*.yaml)"
- "persona YAML (personas/*.yaml)"
- "character sheets (characters/*.yaml)"
plan_phase:
- "series config (colette.yaml) if present"
- "previous stories (for series continuity)"
- "story brief / premise"
do_phase:
- "scene outline from Creator"
- "voice profile for style reference"
check_phase:
- "voice profile (for Sage drift scoring)"
- "outline (for Guardian coherence check)"
- "character sheets (for consistency)"
# Model preferences — writing needs quality for prose generation and review
model_overrides:
maker: sonnet # Prose quality matters more than speed
story-sage: sonnet # Needs taste for voice evaluation
story-explorer: haiku # Research is analytical, haiku suffices
creator: haiku # Outlining is structural, haiku suffices

View File

@@ -0,0 +1,22 @@
# Bundle: writing-short-story
# Complete setup for short fiction writing (5-15k words) with ArcheFlow.
# Based on the Giesing Gschichten dogfood experience.
name: writing-short-story
description: "Short fiction writing setup — premise to polished draft (5-15k words)"
version: "1.0.0"
domain: writing
includes:
team: team.yaml
workflow: workflow.yaml
domain: domain.yaml
config: config.yaml
archetypes:
- story-explorer.md
- story-sage.md
requires: [] # colette.yaml recommended but not required
variables:
target_words: 8000 # Target word count for the story
max_cycles: 2 # PDCA review cycles before forced exit
voice_profile: "" # Path to voice profile YAML (optional)
dialect_density: 0.15 # Target dialect ratio (0 = none, 1 = full dialect)

View File

@@ -0,0 +1,27 @@
# Team: Story Development
# Short fiction team — researches foundations, outlines structure, drafts prose, reviews quality.
# Designed for 5-15k word stories. Works with or without colette.yaml.
name: story-development
description: "Kurzgeschichten-Entwicklung: Recherche, Outline, Draft, Review"
domain: writing
# Plan: story-explorer researches emotional core and plot seeds,
# creator designs scene outline and tension arc.
plan: [story-explorer, creator]
# Do: maker drafts the prose scene by scene.
do: [maker]
# Check: guardian validates plot coherence and continuity,
# story-sage evaluates prose quality and voice consistency.
check: [guardian, story-sage]
exit: all_approved
max_cycles: ${max_cycles}
# Notes:
# - story-explorer and story-sage are custom archetypes (see archetypes/ directory)
# - guardian uses standard archetype with writing domain review_focus overrides
# - creator designs the outline (standard archetype, context-adapted)
# - maker drafts the prose (standard archetype, model override to sonnet for quality)

View File

@@ -0,0 +1,59 @@
# Workflow: Kurzgeschichte
# Short story development — from premise to polished draft.
# Standard PDCA with 2 cycles. Suitable for 5-15k word stories.
name: kurzgeschichte
description: "Short story development — from premise to polished draft"
team: story-development
phases:
plan:
archetypes: [story-explorer, creator]
parallel: false
description: |
1. story-explorer: Research premise, identify emotional core, recommend plot direction.
Read character files, voice profile, and persona rules if available.
2. creator: Design scene outline with character beats, tension arc, and pacing.
Target: ${target_words} words across scenes.
inputs:
- "Story premise / brief"
- "Character files (characters/*.yaml) if available"
- "Voice profile (${voice_profile}) if configured"
- "Persona rules if available"
do:
archetypes: [maker]
parallel: false
description: |
Draft the story following the outline.
Write in scenes, not chapters. Commit after each scene.
Target word count: ${target_words} words.
Dialect density target: ${dialect_density} (0 = none, 1 = full).
inputs:
- "Scene outline from creator"
- "Voice profile for style reference"
- "Character files for consistency"
check:
archetypes: [guardian, story-sage]
parallel: true
description: |
guardian: Plot coherence, character consistency, timeline accuracy, continuity.
story-sage: Prose quality, voice consistency, dialect authenticity.
inputs:
- "Draft from maker"
- "Outline from creator (for guardian)"
- "Voice profile (for story-sage)"
act:
exit_when: all_approved
max_cycles: ${max_cycles}
on_reject: |
Route guardian findings back to creator (outline fix).
Route story-sage findings back to maker (prose fix).
Each fix must be a targeted edit, not a full rewrite.
hooks:
pre_plan: []
post_check: []
post_act: []