🔧 Akira Workflows

System evolution — how the Agentic Hub improves itself over time.

What Akira Does

Akira is the architect and builder identity. While task work is the primary mode, Akira also has meta-workflows for evolving the system itself — updating rules, syncing workflows across workspaces, and distilling learnings into persistent memory.

Commands

/akira (Evolve)

Audit and Evolve

Reviews changes made during the current session and identifies opportunities to update system infrastructure: rules, workflows, documentation, and architecture.

What it does:

  • Review git diff of session changes
  • Identify patterns that should become rules (in .agent/rules/)
  • Update workflows if the process has changed
  • Update documentation if architecture has changed
  • Update CLAUDE.md if project context has shifted
Self-improving system: This is how the Agentic Hub gets smarter over time. Each session's lessons are captured and encoded into the system's rules and workflows, so future sessions start from a better baseline.

/akira sync

Sync Workflows Across Workspaces

Pushes the master workflow files from Agentic Hub to the Dev, Work, and Life workspaces. Ensures all workspaces share the same operational workflows.

What it syncs:

SourceTargets
e:\Agentic\.agent\workflows\e:\Dev\.agent\workflows\
e:\Work\.agent\workflows\
e:\Life\.agent\workflows\

Only shared workflows are synced. Workspace-specific workflows (if any) are left untouched.

/akira reflect

Distill Session Learnings

Reviews the session and extracts learnings worth persisting into memory (.agent/rules/memory.md). Captures people, tools, patterns, and gotchas discovered during work.

What it captures:

  • New people or tools encountered
  • Surprising behaviors or bugs
  • Patterns that worked well (or didn't)
  • Corrections to existing memory entries

Rules System

Akira maintains the rules in .agent/rules/. These are always-on behavioral constraints that shape how agents operate.

Rule FileWhat It Enforces
shell-conventions.md-DisableKeepAlive on HTTPS, no && chaining, ASCII commits
logging-dual-write.mdEvery log to both local file AND D1 API
task-patterns.mdQuery D1 first, never grep local files for task data
DB-golden-truth.mdD1 is read layer, local files are agent caches
no-delete-d1.mdSoft-delete only — PATCH status, never DELETE
always-deploy.mdManual deploy with wrangler, not auto on push
portal-e2e-testing.mdRun tests after portal API changes
session-channel.mdPost session start/end to #dev channel
wellness-awareness.mdPassive stress monitoring, language pattern detection
memory.mdCross-session knowledge store (auto-read on start)

Key Files

FilePurpose
.agent/workflows/akira.mdAkira workflow prompt template
.agent/rules/identity/akira.mdAkira's identity, tone, responsibilities
.agent/rules/memory.mdCross-session persistent memory
.agent/rules/auto-evolve.mdRule for periodic self-improvement
architecture.mdSystem architecture documentation
CLAUDE.mdProject context (read by Claude Code on startup)