Skip to content
Back to skills

Plan Research Daemn256 Workspace Repo Templ

ASecurity

Research a problem space with evidence gathering and source validation.

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
researchgitapidocumentation

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill plan-research-daemn256-workspace-repo-templ --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plan Research Daemn256 Workspace Repo Templ?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Plan Research Daemn256 Workspace Repo Templ
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-plan-research-daemn256-workspace-repo-templ-claude-skill-registry/badge)](https://www.skillsdirectory.com/skills/majiayu000-plan-research-daemn256-workspace-repo-templ-claude-skill-registry)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: plan-research
description: Research a problem space with evidence gathering and source validation.
---

# Plan Research

The Planner drives this workflow. Investigate a problem space by gathering evidence from the codebase, documentation, and external sources. Produce a structured research summary with cited sources.

---

## Phase 1: Scope the Investigation

Define the boundaries before researching.

### Steps

1. State the research question clearly
2. Identify what you need to learn and why
3. Define what is in-scope and out-of-scope
4. List known starting points (files, docs, APIs, prior ADRs)

### Output

Produce a scoped research brief covering: research question, in/out scope, starting points.

**Approval Required:** No

---

## Phase 2: Gather Evidence

Collect evidence from internal and external sources.

### Internal Sources

1. Search the codebase for relevant patterns, implementations, and conventions
2. Read existing ADRs, architecture docs, and design notes
3. Review git history for context on past decisions
4. Quantify where possible (line counts, file counts, dependency counts)

### External Sources

1. Use `WebFetch` to read official documentation, changelogs, or specifications
2. Use `mcp__github__search_repositories` to explore prior art in open source
3. Do NOT rely solely on training knowledge for version-specific behavior, API signatures, or configuration options — verify against the source
4. Cite every external source with a URL or repository reference

### Evidence Standards

- Every claim must link to a specific file, line, URL, or commit
- Distinguish verified facts from inferences
- Note contradictions between sources
- Record what you searched for and didn't find (negative evidence)

### Output

Produce a findings report covering: topic-by-topic findings with sources, negative evidence.

**Approval Required:** No

---

## Phase 3: Synthesize

Combine findings into a structured research summary.

### Steps

1. Combine findings into a coherent picture
2. Identify patterns, gaps, and contradictions
3. State implications for the original research question
4. List open questions that remain unanswered

### Output

Produce a research summary covering: synthesis narrative, key insights (numbered), open questions, sources table (source | type | key finding).

### ⛔ CHECKPOINT

**STOP.** Do not proceed until human confirms the research summary is accurate and sufficient.

**Approval Required:** Yes

---

## Error Handling

| Error                       | Recovery                                                 |
| --------------------------- | -------------------------------------------------------- |
| Research question too broad | Narrow scope, break into sub-questions                   |
| External source unavailable | Note the gap, try alternative sources                    |
| Contradictory evidence      | Document both sides, flag for human judgment             |
| Insufficient evidence       | State what's missing, recommend additional investigation |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.