Christian Nennemann
21becd8b58
The archetypes and shadows are distinctive enough — no need for a fancy name on top of the standard PDCA cycle terminology.
27 lines
761 B
YAML
27 lines
761 B
YAML
# Example: Custom workflow definition
|
|
# Save as .archeflow/workflows/api-design.yaml in your project
|
|
|
|
name: api-design
|
|
description: "API-first workflow with contract validation and adversarial testing"
|
|
|
|
# PDCA workflow configuration
|
|
pdca:
|
|
plan:
|
|
archetypes: [explorer, creator]
|
|
parallel: false # sequential: Explorer feeds Creator
|
|
do:
|
|
archetypes: [maker]
|
|
parallel: false
|
|
check:
|
|
archetypes: [guardian, skeptic, trickster]
|
|
parallel: true # all reviewers run simultaneously
|
|
act:
|
|
exit_when: all_approved
|
|
max_cycles: 2
|
|
feedback_format: diff # pass only the delta between cycles
|
|
|
|
# Optional: final gate runs once after all cycles pass
|
|
final_gate:
|
|
archetypes: [sage]
|
|
description: "Final holistic review before merge"
|