[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Research] Use when a workflow step or the user asks for synthesis of existing evidence into a cited research report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Web Research Protocol — Factual claims need 2+ independent sources; rank Tier 1 authoritative > Tier 2 industry reports > Tier 3 credible blogs; Tier 4 unverified, NEVER cite as fact; declare confidence (95/80/60/<60%). Working files →
tmp/research/; final output →docs/knowledge/.MUST ATTENTION READ only the Knowledge Work Rules (canonical for the research chain) section of
.claude/skills/web-research/SKILL.mdfor canonical research rules; source-discovery procedures belong to a separate discovery request.
Goal: Synthesize the existing evidence base into a fully cited, template-compliant research report with honest confidence and explicit gaps, trustworthy for decisions.
Summary:
tmp/research/_evidence-{slug}.md + _sources-{slug}.md from source-deep-dive into docs/knowledge/research/{slug}.md; do not gather sources — upstream gathering already happened; no alternate mode or flag.[N] citations, per-finding confidence, and Analysis patterns/contradictions; (5) audit citations; (6) roll up confidence, flag <60%, run final review, then retain working evidence for acceptance and repair.[N] and 2+ independent sources; every Sources-table row needs a reference; Tier 4 is NEVER cited as fact; preserve gaps and discrepancies.docs/knowledge/research/{slug}.md, with this run’s tmp/research/ evidence retained through review acceptance.Workflow:
TaskCreate tasks; keep one in_progress; add a final review task..claude/templates/research-report-template.md; retain every section.docs/knowledge/research/{slug}.md; map evidence into each section, cite [N], declare confidence, and record patterns/contradictions in Analysis.<60%; retain this run's source map and evidence base through downstream review and repair; synthesis completion does not authorize cleanup.Key Rules:
[N]; use 2+ independent sources; reference every Sources-table row; Tier 4 is NEVER fact.<60% finding.Be skeptical; apply critical/sequential thinking; trace every claim; state confidence (>80% to act).
Apply the Knowledge Work Rules in .claude/skills/web-research/SKILL.md (read that section first): source tiers, cross-validation, confidence declarations, enforced template, working files under tmp/research/, final output under docs/knowledge/.
Read tmp/research/_evidence-{slug}.md and tmp/research/_sources-{slug}.md.
Inventory total findings with confidence scores, unresolved discrepancies, and remaining gaps.
Read enforced template: .claude/templates/research-report-template.md
Every template section MUST ATTENTION appear in final report.
Write to docs/knowledge/research/{slug}.md. For each template section:
[N]Verify:
[N] citations and 2+ independent sourcesCalculate overall report confidence:
Final report: docs/knowledge/research/{descriptive-slug}.md
Retain this run's tmp/research/_sources-{slug}.md and _evidence-{slug}.md through review and repair. In a workflow, only the orchestrator may clean these exact files after /knowledge-review APPROVED the final artifact and /workflow-end successfully accepted closure; record the acceptance and cleanup in the workflow report. On REVISE, BLOCKED, interruption, or closure failure, keep both files so their owning skills can rerun. Standalone synthesis retains both files until an explicit acceptance or retention policy authorizes cleanup; never delete other files under tmp/research/.
IMPORTANT MUST ATTENTION Goal: Synthesize the existing evidence base into a fully cited, template-compliant research report with honest confidence and explicit gaps, trustworthy for decisions.
IMPORTANT MUST ATTENTION Main path: (1) create small TaskCreate tasks; keep one in_progress; add a final review task; (2) load both evidence files and inventory findings/confidence/discrepancies/gaps; (3) load the enforced template and retain every section; (4) synthesize to docs/knowledge/research/{slug}.md with [N] citations, per-finding confidence, and Analysis patterns/contradictions; (5) audit claim citations, Sources-table coverage, and orphan citations; (6) average scores, weight by importance, flag <60%, run final review, then retain source/evidence inputs until accepted workflow closure or explicit standalone acceptance.
IMPORTANT MUST ATTENTION Mode/boundary: No alternate mode or flag; consume existing source-deep-dive evidence; NEVER gather sources, fabricate, or upgrade findings; retain tmp/research/ source/evidence inputs through review and repair.
IMPORTANT MUST ATTENTION use enforced template structure (.claude/templates/research-report-template.md) — every section required, NEVER omit Knowledge Gaps — why: a missing gaps section manufactures false confidence in incomplete research
IMPORTANT MUST ATTENTION inline-cite every factual claim with [N]; verify zero orphan citations (claim cites missing source) AND zero orphan sources (Sources-table row referenced 0 times) — why: uncited claims are assertions, not findings
IMPORTANT MUST ATTENTION synthesize FROM the evidence base only (tmp/research/_evidence-{slug}.md + _sources-{slug}.md) — NEVER fabricate, add, or upgrade findings beyond gathered evidence; this skill consolidates, it does not research — why: invented findings poison the report's trust
IMPORTANT MUST ATTENTION respect source tiers — Tier 4 (unverified) NEVER cited as fact; every factual claim backed by 2+ independent sources — why: single-source or unverified claims read as confident but unproven
IMPORTANT MUST ATTENTION close with an honest confidence rollup (importance-weighted average of finding scores) that prominently flags every <60% finding — why: an unflagged weak finding inflates apparent report confidence
IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting; mark one in_progress at a time and complete it on evidence
IMPORTANT MUST ATTENTION cite file:line evidence (or [N] source) for every claim — confidence >80% to act, <60% DO NOT assert; NEVER present a guess as fact
IMPORTANT MUST ATTENTION grep/read 3+ similar existing reports under docs/knowledge/research/ before writing — match the template's section shape, do NOT invent a new layout — why: divergent report structure breaks the knowledge-review gate
IMPORTANT MUST ATTENTION output final report to docs/knowledge/research/{slug}.md, retain this run’s working evidence until acceptance authorizes cleanup — why: rejected artifacts need reproducible repair inputs
IMPORTANT MUST ATTENTION add a final review todo task to verify work quality (template complete · citations balanced · gaps present · rollup flagged)
Anti-Rationalization:
| Evasion | Rebuttal |
|---|---|
| "Evidence is thin, fill the gap with my own" | NEVER fabricate. Record it in Knowledge Gaps with confidence <60% instead. |
| "This claim is obvious, skip the citation" | No [N] = not a finding. Cite the source or move it to assumptions. |
| "Gaps section is empty, drop it" | Empty ≠ omit. State "no unresolved gaps" explicitly — omission fakes completeness. |
| "All findings strong, skip the rollup flag" | Compute the weighted average; flag any <60%. One weak finding hides in the mean. |
| "Template section is N/A, delete it" | Keep it, write "Not applicable — why". Missing sections fail the knowledge-review. |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Architecture] Use when a workflow step or the user asks for architecture design, compliance review, scalability grading or whole-project audit via --mode={design|review|scalability|full}.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.