4,961 件 ・ 関連度順
概要と使いどころ
Use when the user asks for a knowledge article, wiki page, or entity summary from the brain, or wants to search, list, or review merges across brain DB articles. Generates Wikipedia-style articles from entities, decisions, and emails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes /coco or /coco!, says catch me up, or asks what needs attention, a project status, their todos, decisions or people. Renders the PM dashboard and routes each subcommand to its platform tool or a PM skill.
日本語の概要は準備中です。原文の説明を表示しています。
Post-run self-evaluation system that scores agent output on correctness, clarity, actionability, and conciseness. Use after /team runs, skill executions, or when explicitly asked to evaluate output quality.
日本語の概要は準備中です。原文の説明を表示しています。
Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".
日本語の概要は準備中です。原文の説明を表示しています。
Run the four paper-quality autoraters from PaperOrchestra (arXiv:2604.05018, App. F.3) — Citation F1 (P0/P1 partition + Precision/Recall/F1), Literature Review Quality (6-axis 0-100 with anti-inflation rules), SxS Overall Paper Quality (side-by-side), and SxS Literature Review Quality (side-by-side). TRIGGER when the user asks to "score this paper draft", "evaluate against the benchmark", "compare two papers", or "run the autoraters".
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, file work only, no browser at all. Walks every AI Employee installed on this machine, reads each one's own run log strictly read only, classifies every routine as running, stopped loudly, stopped silently, or paused, ages the faults, folds the decision register, and writes the one short brief the member opens first. It never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing.
日本語の概要は準備中です。原文の説明を表示しています。
Roadmap concision rules, step decomposition efficiency, AC abstraction guidelines, and step-to-scenario mapping. Load when creating implementation roadmaps.
日本語の概要は準備中です。原文の説明を表示しています。
Design taste evaluation framework — DVF primary filter, Apple/Google/Jobs design principles as explicit scoring criteria, weighted decision matrix, and option ranking for the DIVERGE wave
日本語の概要は準備中です。原文の説明を表示しています。
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence quality validation and decision gate criteria for product discovery reviews
日本語の概要は準備中です。原文の説明を表示しています。
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
日本語の概要は準備中です。原文の説明を表示しています。
Strategic and tactical DDD patterns, bounded context discovery, context mapping, aggregate design rules, and decision frameworks for when to apply DDD
日本語の概要は準備中です。原文の説明を表示しています。
TLA+ and PlusCal for specifying distributed system invariants. Decision heuristics for when formal verification adds value, key patterns, state explosion management, and alternatives comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
日本語の概要は準備中です。原文の説明を表示しています。
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
日本語の概要は準備中です。原文の説明を表示しています。
DIVIO/Diataxis four-quadrant documentation framework - type definitions, classification decision tree, and signal catalog
日本語の概要は準備中です。原文の説明を表示しています。
4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking
日本語の概要は準備中です。原文の説明を表示しています。
7 agentic design patterns with decision tree for choosing the right pattern for each agent type
日本語の概要は準備中です。原文の説明を表示しています。
Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to WRITE a marketing report someone else will read — a one-page weekly for a CEO, a full monthly, or a quarterly strategy report with TL;DR, results versus target, insight, decisions needed, and next actions with owners. Trigger on 'marketing report', 'monthly report', 'weekly update for my boss', 'report for the client', 'quarterly summary', 'turn these numbers into a report'. Also use when the user says a stakeholder is asking how marketing is doing. Not for — diagnosing why the numbers are bad, see `03-performance-eval-global`; turning a raw export into insight, see `13-data-analysis-global`; a closed campaign retrospective, see `63-campaign-retrospective-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
日本語の概要は準備中です。原文の説明を表示しています。