Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
The English summary is being prepared. Showing the original description.
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
The English summary is being prepared. Showing the original description.
Use when property-service operations need an AI plus ontology plus DMAIC design for work orders, dispatch, quotes, evidence, CTQ metrics, and control dashboards.
The English summary is being prepared. Showing the original description.
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.
The English summary is being prepared. Showing the original description.
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
The English summary is being prepared. Showing the original description.
Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
The English summary is being prepared. Showing the original description.
Use when a long-running agent task needs context budgeting, checkpointing, compaction, retrieval, or capability-based model routing.
The English summary is being prepared. Showing the original description.
Use when a defined problem needs diverse ideas, cross-domain combinations, and cheap experiments instead of a single untested answer.
The English summary is being prepared. Showing the original description.
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
The English summary is being prepared. Showing the original description.
Use when a decision-relevant question needs multi-source search, claim-level citations, contradiction handling, uncertainty, or a durable wiki handoff.
The English summary is being prepared. Showing the original description.
Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.
The English summary is being prepared. Showing the original description.
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.
The English summary is being prepared. Showing the original description.
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
The English summary is being prepared. Showing the original description.
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
The English summary is being prepared. Showing the original description.
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
The English summary is being prepared. Showing the original description.
Use when a completed work session should yield durable concepts, corrections, decisions, reusable patterns, and a traceable next action.
The English summary is being prepared. Showing the original description.
Use when a startup needs an evidence-weighted health check, investor lens, runway diagnosis, top constraint, or cheapest next validation test.
The English summary is being prepared. Showing the original description.
Use when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.
The English summary is being prepared. Showing the original description.
Use when a PDF, URL, transcript, clipping, or raw note must become source-grounded, linked, governed knowledge in an Obsidian vault.
The English summary is being prepared. Showing the original description.
Use when an Obsidian wiki needs a reproducible health audit for structure, provenance, links, understanding, lifecycle, and promotion readiness.
The English summary is being prepared. Showing the original description.
Use when manual work, prior sessions, or an operator interview must be audited for repeatable skill, automation, or bounded-loop candidates.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)