agentic-workflow-and-tech-stack

Expertise in designing Claude Code subagents. Use when creating new agents, understanding agent composition, designing agent templates, or learning about agent constraints.

Advises on when to delegate to subagents. Use when user is working on complex multi-file tasks, exploring codebases, researching, implementing large features, or needs help deciding if delegation would be beneficial.

Filesystem-based message passing for agent communication. Use when user asks about agent messaging, inbox/outbox, how agents talk to each other, multi-agent workflows, agent coordination, passing data between agents, agent handoffs, or working around the subagent spawn constraint. Also triggers on "how do I use messaging", "send message to agent", "agent communication".

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

The maintenance program for this scaffold's live knowledge gradient — where captures go (zz-log → zz-research → 02-stack → 01-kernel), the promotion gates between stages (evidence-gating, second-user test, supersession rules), decay review, and retrieval-friendly writing (description-as-semantic-key, one concept per file). Use when capturing insights, promoting notes between stages, deciding where knowledge lives, or reviewing stale docs.

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

Expert in OpenCode permission configuration. Use when user asks about opencode.json, permission allowlists, bash command patterns, or wants to create/configure OpenCode permissions for a project.

Expertise in designing proactive auto-triggering components. Use when creating skills, agents, hooks, or commands that should activate automatically based on context, events, or checkpoints.

SEACOW meta-framework expertise for organizational design. Use when designing structures, analyzing systems, asking 'where should this go', creating conventions for projects/vaults, or understanding organizational patterns.

Expertise in designing Claude Code skills. Use when creating new skills, refining existing ones, designing skill templates, or understanding how skills work.

Use when writing tests, analyzing test results, or improving test coverage. Provides conventions for workflow testing, comment syntax, and improvement patterns.

Concierge for navigating, using, and maintaining this workflow scaffold. Use when users ask about scaffold structure, where things go, conventions, how to get started, how to do scaffold-level work, or when scaffold actions may need delegation to agents. Answers directly when possible; ASKS before spawning agents.

Use PROACTIVELY when creating files, completing tasks, or working in projects with a knowledge-base/ folder. Guides proper use of the temperature gradient system.