nw-research-methodology
Research output templates, distillation workflow, and quality standards for evidence-driven research
Best use case
nw-research-methodology is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Research output templates, distillation workflow, and quality standards for evidence-driven research
Teams using nw-research-methodology should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nw-research-methodology/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How nw-research-methodology Compares
| Feature / Agent | nw-research-methodology | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Research output templates, distillation workflow, and quality standards for evidence-driven research
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Research Methodology
## Research Output Template
Use for all research documents in `docs/research/`.
```markdown
# Research: {Topic}
**Date**: {ISO-8601} | **Researcher**: nw-researcher (Nova) | **Confidence**: {High/Medium/Low} | **Sources**: {count}
## Executive Summary
{2-3 paragraph overview of key findings, main insights, and overall conclusion}
## Research Methodology
**Search Strategy**: {how sources were found}
**Source Selection**: Types: {academic/official/industry/technical_docs} | Reputation: {high/medium-high min} | Verification: {cross-referencing approach}
**Quality Standards**: Target 3 sources/claim (min 1 authoritative) | All major claims cross-referenced | Avg reputation: {0.0-1.0}
## Findings
### Finding 1: {Descriptive Title}
**Evidence**: "{Direct quote or specific data point}"
**Source**: [{Source Name}]({URL}) - Accessed {YYYY-MM-DD}
**Confidence**: {High/Medium/Low}
**Verification**: [{Source 2}]({URL2}), [{Source 3}]({URL3})
**Analysis**: {Brief interpretation or context}
{Repeat Finding structure as needed}
## Source Analysis
| Source | Domain | Reputation | Type | Access Date | Cross-verified |
|--------|--------|------------|------|-------------|----------------|
| {name} | {domain} | {High/Medium-High/Medium} | {academic/official/industry/technical} | {YYYY-MM-DD} | {Y/N} |
Reputation: High: {count} ({%}) | Medium-high: {count} ({%}) | Avg: {0.0-1.0}
## Knowledge Gaps
### Gap 1: {Description}
**Issue**: {missing/unclear info} | **Attempted**: {sources searched} | **Recommendation**: {how to address}
## Conflicting Information (if applicable)
### Conflict 1: {Topic}
**Position A**: {Statement} — Source: [{Name}]({URL}), Reputation: {score}, Evidence: {quote}
**Position B**: {Contradictory statement} — Source: [{Name}]({URL}), Reputation: {score}, Evidence: {quote}
**Assessment**: {Which source more authoritative and why}
## Recommendations for Further Research
1. {Specific recommendation with rationale}
## Full Citations
[1] {Author}. "{Title}". {Publication}. {Date}. {URL}. Accessed {YYYY-MM-DD}.
## Research Metadata
Duration: {X min} | Examined: {count} | Cited: {count} | Cross-refs: {count} | Confidence: High {%}, Medium {%}, Low {%} | Output: docs/research/{filename}
```
## Skill Distillation Workflow
When creating a skill (via `*create-skill` or `skill_for` specified):
### Phase 1: Research
Execute comprehensive research, create full doc in `docs/research/{category}/{topic}-comprehensive-research.md`, complete quality gates.
### Phase 2: Distillation
1. Read comprehensive research
2. Transform: academic -> practitioner-focused
3. Preserve 100% essential concepts (no lossy compression)
4. Remove: verbose explanations, extensive examples, redundant cross-refs
5. Keep: core concepts, practical tools, methodologies, decision heuristics
6. Make self-contained (no external refs) | Target <1000 tokens/file
7. Write to `~/.claude/skills/nw-{skill-name}/SKILL.md{topic}-methodology.md`
### Phase 3: Validation
Verify all essential concepts present | Confirm practitioner focus | Check self-containment
## Quality Standards
### Per-Claim Requirements (Adaptive to Turn Budget)
Source requirements adapt to available turn budget:
- **Ideal**: 3+ independent sources per major claim
- **Acceptable**: 2 credible sources when budget is constrained
- **Minimum**: 1 authoritative source (official docs, RFC, specification) with explicit confidence note
- **Never**: 0 sources -- unsourced claims must be flagged as "[unverified]"
When budget runs low, prioritize BREADTH (cover all claims with minimum sources) over DEPTH (exhaust sources for one claim while ignoring others).
Additional requirements:
- Each source validated against trusted source config from prompt context
- Cross-reference status documented per finding
### Confidence Ratings
- **High**: 3+ high-reputation sources agree, no contradictions
- **Medium**: 2+ agree, minor contradictions or some medium-trust
- **Low**: single source or significant contradictions
### Quality Gates (before finalizing)
1. Every major claim has citations (3+ ideal, 2 acceptable, 1 authoritative minimum) | 2. All sources from trusted domains
3. All findings evidence-backed | 4. Knowledge gaps documented | 5. Output in allowed directories
6. Claims with fewer than 3 sources have confidence rating adjusted accordinglyRelated Skills
nw-tdd-methodology
Deep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policy
nw-research
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.
nw-leanux-methodology
LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation
nw-five-whys-methodology
Toyota 5 Whys methodology with multi-causal branching, evidence requirements, and validation techniques
nw-discovery-methodology
Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.
nw-design-methodology
Apple LeanUX++ design workflow, journey schema, emotional arc patterns, and CLI UX patterns. Load when transitioning from discovery to visualization or when designing journey artifacts.
nw-bdd-methodology
BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation
nw-ux-web-patterns
Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.
nw-ux-tui-patterns
Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.
nw-ux-principles
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
nw-ux-emotional-design
Emotional design and delight patterns for product owners. Load when designing onboarding flows, empty states, first-run experiences, or evaluating the emotional quality of an interface.
nw-ux-desktop-patterns
Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.