c/claude-archeflow-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: address Guardian review findings — sync Creator agent, wire hooks, add cost table

Browse Source 
- Sync agents/creator.md output format with plan-phase skill (3-axis confidence,
  alternatives considered, mini-reflect) — fixes adaptation rule A3 dependency
- Wire hook points into orchestration Act phase (pre-merge, post-merge)
- Add cost-per-agent-tier table to autonomous-mode for budget scheduling
- Add team preset loading reference to orchestration Step 0
This commit is contained in:
Christian Nennemann
2026-04-03 06:23:47 +02:00
parent 761d64b821
commit 8755d68dc9
3 changed files with 39 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
skills/autonomous-mode/SKILL.md
View File

@@ -171,7 +171,15 @@ Budget: $5.00 (or ~2M tokens)
| < 25% | Run remaining tasks as `fast` only |
| Exhausted | Stop. Log remaining tasks as "skipped — budget exhausted" |
Budget is tracked per-task in the session log. Estimated cost = agents spawned x model tier pricing.
Budget is tracked per-task in the session log. Estimated cost per agent by model tier:
| Tier | Model | Est. Cost/Agent |
|------|-------|----------------|
| cheap | Haiku | ~$0.01 |
| standard | Sonnet | ~$0.05 |
| premium | Opus | ~$0.25 |
A standard workflow (6 agents, mostly Sonnet) costs ~$0.30. A thorough workflow (8 agents) costs ~$0.50. These are rough estimates — actual cost depends on context size and output length.
## Auto-Resume on Interruption

9
skills/orchestration/SKILL.md
View File

@@ -9,7 +9,9 @@ This skill guides you through running a full ArcheFlow orchestration using Claud
## Step 0: Choose a Workflow
Assess the task and pick:
If `.archeflow/teams/<name>.yaml` exists, the user can reference a team preset: `"Use the backend team"`. Load the preset's phase config instead of built-in defaults. See `archeflow:custom-archetypes` skill for preset format.
Otherwise, assess the task and pick:
| Signal | Workflow |
|--------|----------|
@@ -252,8 +254,9 @@ Example: "done when pytest passes and Guardian approves with 0 CRITICAL"
If completion criteria are defined, **all criteria must pass** — reviewer approval alone is not sufficient. If tests fail but reviewers approved, cycle back with "tests failing" as feedback to Creator.
### All Approved (and completion criteria met)
1. Merge the Maker's worktree branch into the target branch
2. **Post-merge verification:** Run the project's test suite on the merged branch
1. **Pre-merge hooks:** Check `.archeflow/hooks.yaml` for `pre-merge` hooks. Run them. If `fail_action: abort`, stop and report.
2. Merge the Maker's worktree branch into the target branch
3. **Post-merge hooks:** Run `post-merge` hooks from `.archeflow/hooks.yaml` if defined. Then run the project's test suite on the merged branch
- Tests pass → proceed to step 3
- Tests fail → **auto-revert** the merge commit, report the failure, and cycle back with "integration test failure on main" as feedback
3. Report: what was implemented, what was reviewed, any warnings noted