AI Workflows

Operational workflows for AI development

Documentation, planning, context management, and communication systems for teams building with AI tools.

4 workflows online

contextonline

Brain

Project memory, retrieval, and session hygiene for AI development work.

Use Brain when repo knowledge needs to survive beyond one chat: architecture notes, workflow rules, implementation decisions, risks, and focused context packets.

Commands

brain prep --task "..."brain search "slopstack ..."brain session run -- npm run lint

Best for

  • Loading the right repo context before edits
  • Capturing decisions after meaningful changes
  • Keeping agent sessions auditable
memoryretrievalsessionscontext
Read related guide
planningonline

Plan

Spec-first planning for turning ideas into scoped execution contracts.

Use Plan when an idea needs shaping before implementation: brainstorm, refine, challenge, promote to spec, and execute with traceable scope.

Commands

plan status --project .plan brainstorm start --project . "..."plan spec execute --project . <spec-slug>

Best for

  • Separating discovery from implementation
  • Keeping specs canonical
  • Avoiding vague multi-feature work
specsroadmapbrainstormexecution
Read related guide
communicationonline

Caveman

Token-efficient agent communication that keeps technical signal intact.

Use Caveman when speed and low-token communication matter. It strips filler while preserving exact technical names, commands, risks, and code.

Commands

/caveman lite/caveman full/caveman ultra

Best for

  • Long debugging sessions
  • Low-noise code reviews
  • Fast status updates with exact commands
tokenscommunicationskillsworkflow
Read related guide
documentationonline

Agent Docs

AGENTS.md plus focused docs for reusable project instructions.

A lightweight documentation pattern for AI coding tools: keep the root contract small, then route agents to architecture, content, UI, and task guides only when needed.

Commands

Read AGENTS.mdUpdate docs/ when workflows change

Best for

  • Reducing repeated project orientation
  • Keeping repo conventions discoverable
  • Sharing workflow knowledge across tools
agents.mddocsskillsinstructions
Read related guide