chore: trim sprint and using-archeflow skills for context efficiency
sprint: 302 -> 164 lines (removed pseudocode, redundant tables, Prerequisites) using-archeflow: 185 -> 55 lines (removed archetypes table, PDCA diagram, progress indicators, dry-run example, full skills reference)
This commit is contained in:
@@ -5,180 +5,51 @@ description: Use at session start when implementing features, reviewing code, de
|
||||
|
||||
# ArcheFlow -- Active
|
||||
|
||||
Multi-agent orchestration using archetypal roles and PDCA quality cycles.
|
||||
|
||||
## Session Start
|
||||
|
||||
On activation, print ONE line:
|
||||
On activation, print ONE line then proceed silently:
|
||||
```
|
||||
archeflow v0.7.0 · 25 skills · <domain> domain
|
||||
```
|
||||
Where `<domain>` is auto-detected: `writing` if `colette.yaml` exists, `research` if paper/thesis files exist, `code` otherwise. Then proceed silently — no further announcement unless `archeflow:run` is invoked.
|
||||
Domain auto-detected: `writing` if `colette.yaml` exists, `research` if paper/thesis files, `code` otherwise.
|
||||
|
||||
During runs, follow the `archeflow:presence` skill for output format: show outcomes not mechanics, one line per phase, value at the end.
|
||||
## When to Use What
|
||||
|
||||
## IMPORTANT: When to Use What
|
||||
|
||||
### Use `/af-sprint` (primary mode) when:
|
||||
- User says "run the sprint", "work the queue", "go autonomous"
|
||||
- Multiple tasks are pending across projects
|
||||
- The workspace queue (docs/orchestra/queue.json) has pending items
|
||||
|
||||
### Use `/af-review` when:
|
||||
- User wants to review code before merging
|
||||
- A diff, branch, or commit range needs quality check
|
||||
- Security-sensitive changes need Guardian analysis
|
||||
|
||||
### Use `/af-run` (deep orchestration) when:
|
||||
- **Writing/research tasks** -- archetypes add value where linters don't exist
|
||||
- **Security-sensitive code changes** -- auth, encryption, API keys
|
||||
- **Complex multi-module refactors** with unclear approach
|
||||
|
||||
### Do NOT use ArcheFlow for:
|
||||
- **Single-feature code development** -- use `feature-dev` plugin or work directly
|
||||
- **Simple fixes** -- just do them
|
||||
- **Questions, exploration, reading** -- no code changes needed
|
||||
|
||||
Choose the workflow based on risk:
|
||||
|
||||
| Signal | Workflow | Command |
|
||||
|--------|----------|---------|
|
||||
| Small fix, low risk, single concern | `fast` | Creator --> Maker --> Guardian |
|
||||
| Feature, multiple files, moderate risk | `standard` | Explorer + Creator --> Maker --> Guardian + Skeptic + Sage |
|
||||
| Security-sensitive, breaking changes, public API | `thorough` | Explorer + Creator --> Maker --> All 4 reviewers |
|
||||
| Need | Command | When |
|
||||
|------|---------|------|
|
||||
| **Work the queue** | `/af-sprint` | Multiple tasks pending across projects, "run the sprint" |
|
||||
| **Deep orchestration** | `/af-run` | Writing/research tasks, security-sensitive code, complex multi-module refactors |
|
||||
| **Code review** | `/af-review` | Review diff/branch/commits before merging, security-sensitive changes |
|
||||
| **Single feature** | `feature-dev` or direct | Clear scope, one project -- no orchestration needed |
|
||||
|
||||
## When to Skip ArcheFlow
|
||||
|
||||
Do NOT use ArcheFlow for these -- just do them directly:
|
||||
Do NOT use for: single-line fixes, questions, reading/exploring, config tweaks, git ops.
|
||||
|
||||
- Single-line fixes, typos, formatting
|
||||
- Answering questions (no code changes)
|
||||
- Reading/exploring code without making changes
|
||||
- Config changes to a single file
|
||||
- Git operations (commit, push, branch)
|
||||
## Workflow Selection
|
||||
|
||||
**Mini-Reflect fallback:** Even when skipping ArcheFlow, apply a quick reflection for non-trivial single-file changes: (1) restate what you're changing, (2) name one assumption, (3) check if it could break anything. This takes ~10 seconds and catches misunderstandings before they become commits.
|
||||
|
||||
## Archetypes
|
||||
|
||||
| Archetype | Avatar | Virtue | Shadow | Phase |
|
||||
|-----------|--------|--------|--------|-------|
|
||||
| **Explorer** | 🔍 | Contextual Clarity | Rabbit Hole | Plan |
|
||||
| **Creator** | 🏗️ | Decisive Framing | Over-Architect | Plan |
|
||||
| **Maker** | ⚒️ | Execution Discipline | Rogue | Do |
|
||||
| **Guardian** | 🛡️ | Threat Intuition | Paranoid | Check |
|
||||
| **Skeptic** | 🤔 | Assumption Surfacing | Paralytic | Check |
|
||||
| **Trickster** | 🃏 | Adversarial Creativity | False Alarm | Check |
|
||||
| **Sage** | 📚 | Maintainability Judgment | Bureaucrat | Check |
|
||||
|
||||
## PDCA Cycle
|
||||
|
||||
```
|
||||
Plan --> Explorer researches, Creator proposes
|
||||
Do --> Maker implements in isolated worktree
|
||||
Check --> Reviewers assess in parallel (approve/reject)
|
||||
Act --> All approved? Merge. Issues? Cycle back to Plan.
|
||||
```
|
||||
|
||||
## Progress Indicators
|
||||
|
||||
During orchestration, emit phase markers so the user can track progress:
|
||||
|
||||
```
|
||||
--- ArcheFlow: <task> -------------------------
|
||||
Workflow: standard (2 cycles max)
|
||||
|
||||
🔍 [Plan] Explorer researching... done (35s)
|
||||
🏗️ [Plan] Creator designing proposal... done (25s, confidence: 0.8)
|
||||
⚒️ [Do] Maker implementing... done (90s, 4 files, 8 tests)
|
||||
🛡️ [Check] Guardian reviewing... APPROVED
|
||||
🤔 [Check] Skeptic challenging... APPROVED (1 INFO)
|
||||
📚 [Check] Sage reviewing... APPROVED
|
||||
[Act] All approved -- merging... merged to main
|
||||
|
||||
--- Complete: 3m 10s, 1 cycle -----------------
|
||||
```
|
||||
|
||||
Update each line as agents complete. This gives the user real-time visibility without interrupting the flow.
|
||||
|
||||
## Dry-Run Mode
|
||||
|
||||
When the user asks "what would ArcheFlow do?" or uses `--dry-run`, show the plan without executing:
|
||||
|
||||
```
|
||||
Dry run for: "Add JWT authentication"
|
||||
Workflow: standard (2 cycles)
|
||||
Agents: 🔍 Explorer --> 🏗️ Creator --> ⚒️ Maker --> 🛡️ Guardian + 🤔 Skeptic + 📚 Sage
|
||||
Est. agents: 6 per cycle, 12 max
|
||||
Worktree: yes (isolated branch)
|
||||
Proceed? [y/n]
|
||||
```
|
||||
|
||||
## Quick Start
|
||||
|
||||
When the user gives an implementation task:
|
||||
|
||||
1. Assess: does this need ArcheFlow? (see criteria above)
|
||||
2. If yes: load `archeflow:orchestration` skill
|
||||
3. Pick workflow (fast/standard/thorough)
|
||||
4. Execute the PDCA steps from the orchestration skill
|
||||
5. Emit progress indicators throughout (see above)
|
||||
| Signal | Workflow | Pipeline |
|
||||
|--------|----------|----------|
|
||||
| Small fix, low risk | `fast` | Creator --> Maker --> Guardian |
|
||||
| Feature, multi-file, moderate risk | `standard` | Explorer + Creator --> Maker --> Guardian + Skeptic + Sage |
|
||||
| Security, breaking changes, public API | `thorough` | Explorer + Creator --> Maker --> All 4 reviewers |
|
||||
|
||||
## Available Commands
|
||||
|
||||
| Command | What it does |
|
||||
|---------|-------------|
|
||||
| `archeflow:run` | Automated PDCA loop -- single command to orchestrate a full run |
|
||||
| `archeflow:orchestration` | Load manual PDCA execution guide |
|
||||
| `archeflow:shadow-detection` | Load shadow monitoring rules |
|
||||
| `archeflow:autonomous-mode` | Load autonomous/overnight session protocol |
|
||||
| `archeflow:status` | Show current orchestration state (phase, cycle, active agents) |
|
||||
| `archeflow:history` | Show past orchestration summaries from `.archeflow/session-log.md` |
|
||||
| `/af-sprint` | Queue-driven parallel agent runner (primary mode) |
|
||||
| `/af-run <task>` | PDCA orchestration loop (`--dry-run`, `--start-from`, `--workflow`) |
|
||||
| `/af-review` | Guardian-led code review on diff/branch/range |
|
||||
| `/af-status` | Current run state, active agents, findings |
|
||||
| `/af-report` | Full process report for a run |
|
||||
| `/af-init` | Initialize ArcheFlow in a project |
|
||||
| `/af-score` | Archetype effectiveness scores |
|
||||
| `/af-memory` | Cross-run lesson memory |
|
||||
| `/af-fanout` | Colette book fanout via agents |
|
||||
| `/af-dag` | DAG of current/last run |
|
||||
|
||||
### `archeflow:status`
|
||||
Read `.archeflow/state.json` (if exists) and report:
|
||||
- Current task, phase, and cycle
|
||||
- Active agents and their status
|
||||
- Findings so far (by severity)
|
||||
- Time elapsed
|
||||
## Mini-Reflect Fallback
|
||||
|
||||
### `archeflow:history`
|
||||
Read `.archeflow/session-log.md` and show the last 5 orchestration summaries in compact format.
|
||||
|
||||
## Skills Reference (All 24)
|
||||
|
||||
### Core Orchestration
|
||||
- **archeflow:run** -- Automated PDCA execution loop with `--start-from` and `--dry-run`
|
||||
- **archeflow:orchestration** -- Step-by-step manual execution guide
|
||||
- **archeflow:plan-phase** -- Explorer and Creator output formats and protocols
|
||||
- **archeflow:do-phase** -- Maker implementation rules and worktree commit strategy
|
||||
- **archeflow:check-phase** -- Shared reviewer protocols and output format
|
||||
- **archeflow:act-phase** -- Post-Check decision logic: collect findings, route fixes, exit or cycle
|
||||
|
||||
### Quality and Safety
|
||||
- **archeflow:shadow-detection** -- Quantitative dysfunction detection and correction
|
||||
- **archeflow:attention-filters** -- Context optimization per archetype
|
||||
- **archeflow:convergence** -- Detects convergence, stalling, and oscillation in multi-cycle runs
|
||||
- **archeflow:artifact-routing** -- Inter-phase artifact protocol for naming, storage, and routing
|
||||
|
||||
### Process Intelligence
|
||||
- **archeflow:process-log** -- Event-sourced JSONL logging with DAG parent relationships
|
||||
- **archeflow:memory** -- Cross-run learning from recurring findings
|
||||
- **archeflow:effectiveness** -- Archetype scoring on signal-to-noise, fix rate, cost efficiency
|
||||
- **archeflow:progress** -- Live progress file watchable from a second terminal
|
||||
|
||||
### Integration
|
||||
- **archeflow:colette-bridge** -- Bridges ArcheFlow with the Colette writing platform
|
||||
- **archeflow:git-integration** -- Git-per-phase commits, branch-per-run, rollback
|
||||
- **archeflow:multi-project** -- Cross-repo orchestration with dependency DAG and shared budget
|
||||
|
||||
### Configuration
|
||||
- **archeflow:custom-archetypes** -- Create domain-specific roles
|
||||
- **archeflow:workflow-design** -- Design custom workflows with per-phase archetype assignment
|
||||
- **archeflow:domains** -- Domain adapters for writing, research, and non-code workflows
|
||||
- **archeflow:cost-tracking** -- Budget enforcement and model tier recommendations
|
||||
- **archeflow:templates** -- Template gallery for sharing workflows, teams, and setup bundles
|
||||
- **archeflow:autonomous-mode** -- Unattended overnight sessions
|
||||
|
||||
### Meta
|
||||
- **archeflow:using-archeflow** -- This skill: session-start activation and quick reference
|
||||
Even when skipping ArcheFlow, apply for non-trivial changes:
|
||||
1. Restate what you're changing
|
||||
2. Name one assumption
|
||||
3. Check if it could break anything
|
||||
|
||||
Reference in New Issue
Block a user