調査、論文、教育、資格学習（4,361 件）
Turns past decisions into calibrated judgment - scoring old predictions against what happened, assigning credit for delayed results, and separating a bad decision from a good decision that lost. Use during a retrospective, postmortem, quarterly or monthly review, when reviewing decisions taken 30+ days ago, when attributing a result to a cause, or when someone claims to have called something.
日本語の概要は準備中です。原文の説明を表示しています。
Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.
日本語の概要は準備中です。原文の説明を表示しています。
Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.
日本語の概要は準備中です。原文の説明を表示しています。
Research the codebase to answer a question without making any changes. Use when exploring code, understanding architecture, or investigating how something works.
日本語の概要は準備中です。原文の説明を表示しています。
Extract learnings from the current session and update memory/config. Use when: learn from this, what did we learn, update memory, session retrospective, extract patterns, save learnings.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when a workflow step or the user asks for deep analysis of a prior source map: fetch, extract and cross-validate findings into a cited evidence base.
日本語の概要は準備中です。原文の説明を表示しています。
Research one agent harness's release (docs, source, runtime) and fill its capability cells in scripts/harness_capabilities.py with cited evidence. Use after a harness version bump, when just harness-probe reports re-research, or when capability cells read unknown.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct market research on competition and customers. Use when the user says they need market research
日本語の概要は準備中です。原文の説明を表示しています。
Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry
日本語の概要は準備中です。原文の説明を表示しています。
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report
日本語の概要は準備中です。原文の説明を表示しています。
Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Research web sources and produce a cited, reviewed deliverable. --output={synthesis|business-eval|marketing|course}.
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when a workflow step or the user asks for tech-stack research: alternatives, trade-offs and user-validated recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when a workflow step or the user asks for web source discovery and triage into a source map and gaps. --chain=deep-dive also builds a cross-validated evidence base.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when a workflow step or the user asks for synthesis of existing evidence into a cited research report.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when a workflow step or the user asks for market analysis: competitors, TAM/SAM/SOM, trends, SWOT and customer segments.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when teaching Claude a lesson that persists across sessions, including an extra rule for one skill or task kind (routes to project-skill-protocol).
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when a workflow step or the user asks for knowledge artifact review: completeness, citation accuracy, confidence and template compliance.
日本語の概要は準備中です。原文の説明を表示しています。
- Entry point for open-source intelligence, investigation and verification work. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise
日本語の概要は準備中です。原文の説明を表示しています。
- Corporate due-diligence workflow — resolve a brand or website to its registered legal entity, map group structure and beneficial ownership, profile officers and directors, enumerate the digital estate, and screen litigation, insolvency,… Use when asked to check out, vet or research a company, verify a supplier or counterparty before signing or paying, or assess whether a business is real
日本語の概要は準備中です。原文の説明を表示しています。
Researches Reddit using a brand's Brand DNA to find promotable pain-point discussions, target subreddits, and real user search language. Produces a prioritized Reddit opportunity list for content seeding, helpful replies, and prompt research inspiration.
日本語の概要は準備中です。原文の説明を表示しています。