Remove verbose YAML examples, bash pseudo-code, tutorial prose, and motivational content from configuration/integration skills while preserving all operational protocols, reference tables, and rules. Skills trimmed: domains, colette-bridge, multi-project, cost-tracking, git-integration, custom-archetypes, workflow-design, templates, autonomous-mode, progress, presence.
1.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| presence | Defines how ArcheFlow communicates its activity to the user -- visible but not noisy. Show value, not process. Auto-loaded by the run skill. |
ArcheFlow Presence -- Visible Value, Not Noise
Output Rules
- Show outcomes, not mechanics
- One line per phase, not per agent
- Numbers over words
- Silence on clean passes
- Value summary at the end
Status Line Format
Run start:
-- archeflow -- <task> -- <workflow> (<max_cycles> cycles) --
Phase complete (only if noteworthy):
V plan explorer: 3 directions -> chose C | creator: 6 scenes
V do 6004 words drafted
T check guardian: 1 fix needed | sage: 5 voice adjustments
V act 6 fixes applied
Symbols: V = clean, T = issues found, X = failed/blocked.
Run complete:
-- done -- 1 cycle . 5 agents . 6 fixes . ~22 min --
story drafted, reviewed, and polished. see stories/01-der-huster.md
Activation indicator (session start, one line):
archeflow v0.7.0 . 24 skills . writing domain detected
When to Be Silent
- Agent spawning/completion lifecycle
- Event emission
- Artifact routing
- Clean review passes (0 findings)
- Phase transitions with no visible output
When to Speak
- Run start and complete (always)
- Findings found and fixes applied
- Budget warnings
- Shadow detected
- User decision needed