Workflows & Commands
32 slash commands organized by the Two Loops — from vision alignment to knowledge distillation. Invoked from VS Code (copilot), Bifrost (automated), or Portal CLI.
Overview
Workflows are slash commands defined in .agent/workflows/. They encode repeatable processes —
from processing feedback to archiving tasks to evolving the system itself. Each workflow is a markdown file
with a prompt template that an agent executes.
Workflows can be triggered in three ways:
🖥️ Copilot (VS Code)
Type the command in Claude Code or Gemini: /clara sweep, /task done, etc. The
agent in your terminal executes it interactively.
🤖 Automated (Bifrost)
Submit via Portal Inbox (Workflow or Clara mode). Bifrost runs it autonomously — no VS Code needed.
⌨️ Portal CLI
Use the portal CLI for CRUD operations on D1 entities: portal task create,
portal log create, etc.
Two Loops System Map
All workflows map to the Creation Loop (building), the Insight Loop (learning), or cross-cutting Infrastructure.
🔨 CREATION LOOP (創造) — purpose → reality (exhale) /task [start|save|done|archive|spawn|delegate] /project [create|list|analyze] /creation-loop [map|trace|gaps|health] /vision [align|check|scan] /problem [dump|triage] /focus, /worthit, /write-blog 💡 INSIGHT LOOP (升華) — experience → wisdom (inhale) /learn [default|scan] /distill [run|session|batch] /wiki [route|create|sync] /research [default|evaluate] /discuss [score|analyze|probe|derive] /clarity [default|report] ⚙️ INFRASTRUCTURE — serves both loops /commit, /log, /ongoing, /remind, /status /hub-evolve, /hub-compact, /hub-audit, /hub-clean, /hub-archive /session [save|summary|health|quality], /handoff /wrapup [session|day] /clara [default|focus], /ingest /pullall, /pushall /mozi
Workflow Deep Dives
DISPATCH ☀️ Clara
Dispatch agent — inbox processing, task classification, priority management. 5 modes: sweep, tidy, archive, focus, align.
CREATION 📋 Task Lifecycle
Start, save, done, archive, spawn, delegate. The full journey of a work unit from creation to completion.
EVOLUTION 🔧 Hub Evolution
System self-improvement — hub-evolve, hub-compact, hub-audit, hub-clean. The closed maintenance loop.
TRACKING 📈 Tracking
Logging, status checks, wrap-ups, velocity. Keep the system informed and the human oriented.
Complete Command Reference
🔨 Creation Loop
| Command | Modes | What It Does |
|---|---|---|
/task |
start, save, done, archive, spawn, delegate | Full task lifecycle — create folder, checkpoint, complete with log+commit |
/project |
create, list, analyze | Bottom-up project grouping. PM-style analysis and status tracking |
/creation-loop |
map, trace, gaps, health | Maintain cohesion across Vision → Nexus → Problems → Projects → Tasks |
/vision |
align, check, scan | Strategic alignment — pulse check against the recursive purpose chain |
/problem |
dump, triage | Externalize pain points. Categorize: 🔴 Solve, 🟡 Bear, 🟢 Accept |
/focus |
— | Laser focus — verify problem statement, corner Adrian to clarity |
/worthit |
— | Challenge an idea — sparring partner against "做得到 ≠ 该做" blindspot |
/write-blog |
— | Create blog post from session insights. Default workspace: Work |
💡 Insight Loop
| Command | Modes | What It Does |
|---|---|---|
/learn |
default, scan | Extract learnings from session — classify by context level — store in memory/rules/KB |
/distill |
run, session, batch | Process long-form content → extract, classify, propose, review, merge |
/wiki |
route, create, sync | Manage wiki ecosystem — route content across wiki instances |
/research |
default, evaluate | Conduct structured research or evaluate AI/tech links. Score and report |
/discuss |
score, analyze, probe, derive | Discussion mode — thinking without execution. 推演 (derive) for implications |
/clarity |
default, report | Measure and track crystallization of project context and readiness |
⚙️ Infrastructure
| Command | Modes | What It Does |
|---|---|---|
/clara |
default, focus | Dispatch: pull portal feedback + local inbox, classify, route to workspaces |
/ingest |
— | Ingest organized Smart Todo items → route to D1 tasks, ongoing, or KB |
/commit |
— | Git commit with conventional commit format + batching strategy |
/log |
— | Create session log with velocity tracking (dual-write: local + D1) |
/ongoing |
— | Manage parallel ongoing tasks in ws/ongoing.md |
/status |
— | Quick daily status check — read-only pulse (no commits) |
/remind |
— | Quick add to ws/agent-notes.md for future sessions |
/session |
save, summary, health, quality | Session capture, health checks, and quality ratings |
/handoff |
— | Gracefully save state and pass work to a new session |
/wrapup |
session, day | End session/day — orchestrates /learn, /log, /commit, /hub-evolve |
/hub-evolve |
— | Sync stale docs/rules/workflows after hub infrastructure changes |
/hub-compact |
— | Compress: derive stale mental models, score clarity, merge/retire/rewrite |
/hub-audit |
— | Deep scan against principles (CE, SC, AQ, OP, SU). File findings |
/hub-clean |
— | Data hygiene — log integrity, task consistency, git health |
/hub-archive |
— | Archive done tasks, old logs, and linked reports |
/pullall |
— | Git pull across all 4 workspaces + nested submodules |
/pushall |
— | Push all 4 root workspaces + nested submodules to GitHub |
/mozi |
— | Mozi practice — awareness training, logout meditation |
Composability Layers
Workflows follow the UNIX philosophy — each does one thing well. Complex operations compose atomic ones:
| Layer | Description | Workflows |
|---|---|---|
| ⚡ Atomic | Single action, no side effects | /commit, /log, /ongoing, /discuss, /status, /remind |
| 🔨 Creation | Track work from vision to completion | /task, /project, /creation-loop, /vision, /problem, /focus, /worthit |
| 💡 Insight | Absorb and refine knowledge | /learn, /distill, /wiki, /research, /clarity |
| 🟠 Session | Capture, assess, transition | /session, /handoff |
| 🎯 Orchestrator | Compose atomics into sequences | /wrapup, /clara, /ingest |
Composition Map
/wrapup ─────┬─ /session save (if discussion)
├─ /learn (Insight Loop)
├─ /learn scan (Insight Loop)
├─ /hub-evolve (Infra)
├─ /task done ─── /ongoing (Creation Loop)
├─ /log
└─ /commit
/handoff ────┬─ /task spawn (if scope grew)
└─ suggests → /wrapup
/task save ──┬─ /commit
└─ /log
Hub Maintenance Cycle (CE10)
A closed loop that keeps the system healthy:
Decision Flow — "What Do I Call?"
Session ending?
├─ YES → Context degraded?
│ ├─ YES → /handoff → /wrapup
│ └─ NO → /wrapup
│
└─ NO → What am I doing?
├─ Creating (🔨) → /task save or /commit
├─ Inhaling (💡) → /distill | /learn | /research
├─ Need direction → /vision | /clara | /creation-loop
├─ Quick pulse → /status
├─ Discussion → /discuss
└─ Process inbox → /clara
Workflow Usage Tracking
Every workflow invocation is logged via portal usage track (CE8 flywheel — usage data feeds
optimization). Analysis happens during /hub-audit or /hub-evolve.
For Agents
.agent/workflows/. Each is a markdown file
with a prompt template. To add a new workflow, create the file and it becomes available as a slash command.
Identity files for named agents (Clara, Akira) are at .agent/rules/identity/.