How to recognize when an agent loop fits, when it doesn't, and how to set one up safely. Use when the user asks "should I loop this", "set up a loop", "automate / run this repeatedly", "babysit my PRs", "run it on a schedule / unattended", mentions /loop, /goal, ralph, or a long-running batch over many items — or when you're about to do the same kind of task many times by hand and a loop might be better. Recommend loops; do not reach for one by default.
Decide whether to use optional active context in a Vivary-backed codebase, especially CocoIndex-code semantic search. Use when a task spans unfamiliar code, exact names are unknown, grep is too thin or too noisy, the user asks about CocoIndex/ccc/active context, or the workspace needs a fresh semantic retrieval pass before implementation or review.
Bootstrap, maintain, and continuously improve a Vivary agent workspace so each session adds momentum the next inherits. Lays down the workspace's shared brain (SOUL/USER/AGENTS/MEMORY/STATE) from strato's templates, runs periodic heartbeats to surface stale folders and skill candidates, captures recurring bugs into a self-healing playbook, and extracts a skill once a workflow repeats a third time. Use when starting a new workspace, when something keeps biting, when a workflow has fired three times, or when the user says "bootstrap the workspace", "set up the brain", "run a heartbeat", "audit the workspace", "tend the workspace", "this happened again", or "strato".
Manage a Markdown knowledge base or any repo's docs with tropo — a folder-as-type typed-knowledge layer where the filesystem IS the schema. Use when the user wants to validate/enforce document metadata, set up a typed vault or docs/ tree, see what a vault actually asserts, strip redundant frontmatter, add a document type or an overlay rule, or scaffold a tropo config. Triggers: "check the vault", "enforce a schema on my notes", "what types of docs do I have", "set up tropo here", "de-noise my frontmatter", "add a type", "lint my Markdown metadata", "tropo".