ywc-tech-research

name: ywc-tech-research description: >- (ywc) Use when comparing libraries, investigating implementation approaches, evaluating technology options, or gathering sourced best practices before a plan/spec decision. Triggers: "기술 조사", "라이브러리 비교", "research", "investigate options", "compare options", "어떤 걸 쓸까", "best way to implement", "技術調査", "ライブラリ比較", "実装方針調査". Do not use for writing the spec itself (use ywc-spec-writer), validating an existing spec (use ywc-spec-validate), code generation (use ywc-code-gen), or simple documentation lookup with no comparison/evaluation decision.

ywc-tech-research

Announce at start: "I'm using the ywc-tech-research skill to investigate options and produce a structured comparison."

Research Agent Skill for technical investigation and library comparison.

Rationalization Defense

When tempted to skip a step, check this table first:

Violating the letter of these rules is violating the spirit. Research without verifiable sources is opinion.

Arguments

Parse $ARGUMENTS for:

Execution Steps

1. Collect Project Context — Read CLAUDE.md, package.json, and directory structure to identify the current tech stack and any constraints (runtime, license, bundle size).

2. Plan Research Strategy — Determine approach based on topic characteristics:

   • Library comparison → official docs + package registry stats + GitHub activity
   • Implementation approach → official docs + code examples + existing project patterns
   • Architecture decision → technical blogs + comparable case studies + trade-off analysis

3. Gather Information — Use sources in this priority order:

   Step 3a — context7 MCP (required, not optional)

   Always query context7 before any web search. context7 returns curated, version-pinned documentation that training data cannot guarantee. Skip context7 only if it explicitly returns no results for the topic — in that case, note the fallback in the References section.

   mcp__context7__resolve-library-id(libraryName: "<library>")
   mcp__context7__query-docs(context7CompatibleLibraryID: "<id>", topic: "<topic>")
   

   Step 3b — Official documentation and package registries

   Supplement context7 with direct official docs. For any source, check the last-updated date:

   • Prefer documentation updated within the last 12 months
   • Flag sources older than 2 years as [potentially stale] in the References section
   • Distinguish official docs from community resources (Stack Overflow, blogs) — present them separately

   Step 3c — --compare parallel mode

   When --compare "A,B[,C...]" is specified, spawn one research subagent per option in parallel via Codex subagent tools, each with the same project context and quality criteria. Collect all results before synthesizing — do not synthesize from partial results.

4. Verify Source Recency — Before writing the report, confirm:

   • At least one official source per option was found
   • Each official source has a visible last-updated date or release version
   • If only community sources are available, state this explicitly in the report

5. Analyze and Output Report — Write a structured report focused on compatibility with the current project stack.

Source Discipline Rules

These rules apply to every claim in the report, regardless of --depth level. They exist to prevent confident-sounding hallucination from polluting technical decisions.

1. Every factual claim must cite a source — write [source: <url or "context7">] inline after the claim. If no source was found, write [source: NOT FOUND — inference only].
2. Distinguish fact from inference — prefix inferred claims with [INFERRED]. Inferences are acceptable, but must be labeled so readers can weigh them appropriately.
3. Cross-reference single-source claims — any claim with only one source and high decision impact (e.g., "library X has known security issues") must be confirmed with a second source before being reported as fact. If a second source cannot be found, label it [SINGLE SOURCE — verify before acting].
4. Prefer sources ≤12 months old — sources older than 12 months must be flagged with [potentially stale: <date>]. Sources older than 2 years should not be cited without an explicit caveat.
5. Acknowledge gaps explicitly — if a required Quality Criteria axis cannot be sourced, write the full N/A — no data found entry. Never omit a row silently.
6. No gap-filling from training data alone — Claude's internal knowledge may be used to explain concepts, but version numbers, benchmark figures, and security advisories must come from a verifiable external source fetched in this session.

Research Quality Criteria

Every option in a comparative analysis must be assessed on all axes below. If data for an axis is unavailable, write N/A — no data found rather than omitting the row.

Output Format

Output depth is controlled by --depth (default: 50):

## Research Result: {topic}

### Summary
(1-2 sentence key conclusion. Inferences labeled [INFERRED].)

### Comparative Analysis
| Option | Pros | Cons | Ecosystem Health | License | Source Age | Fit |
|--------|------|------|-----------------|---------|------------|-----|
(At --depth 75/100: each cell's key claim includes inline [source: …] citation)

### Recommended Approach
(Recommendation with rationale, citing specific axes from the table above.
 Any inference prefixed with [INFERRED]. Any single-source claim marked [SINGLE SOURCE — verify before acting].)

### Project-Specific Considerations
(Compatibility with current stack, migration cost, known conflicts)

### References
- [Official] {name} — {url} (last updated: {date})
- [Community] {name} — {url} (flagged [potentially stale: <date>] if >12 months old)
- [context7] used: yes/no — if no, state the reason

### Completion Status
(One of: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT)

Completion Status rules:

Validation

Before returning the recommendation, verify that official sources were checked first, source dates are present, stale/community-only evidence is labeled, unsupported claims are marked [INFERRED], and the final status reflects any missing benchmark or compatibility evidence.

Integration

• upstream: None (standalone execution)
• downstream: Used as reference material when writing specifications or as input to ywc-task-generator