AgentStack
SKILL verified MIT Self-run

Project Research

skill-cormff-claude-code-playbook-project-research · by cormff

Research and data-gathering phase for {PROJECT} — domain knowledge, reference data models, external API details, and a gap analysis against what already exists. Called by project-orchestrator when a module/topic's knowledge is missing; also used directly when the user says "research {PROJECT}'s X module.

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-cormff-claude-code-playbook-project-research

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Project Research? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

{PROJECT} Research

Produces one accessible, cross-linked vault note per module/topic — not a one-off answer that disappears at the end of the conversation.

Step 1 — Scope the module/topic

Identify what's being researched and where its note should live under {PROJECT_NOTES_PATH}.

Step 2 — Gather

  • Domain knowledge relevant to this module.
  • Reference data models or prior art, internal or external.
  • Any external system/API details this module needs to integrate with.

Delegate to a subagent whenever this involves scanning multiple sources — see [05 — Agents & Delegation](../../../docs/05-agents-and-delegation.md).

Step 3 — Gap analysis

Explicitly compare "what exists already" against "what this module needs" and call out the gap — this is the part most likely to get skipped if research turns into a generic summary instead of decision-relevant input for the design phase.

Step 4 — Write the note

Follow [vault-format](../../layer-0-foundation/vault-format/SKILL.md) conventions; link it from the project's map/hub. This note is what [project-design](../project-design/SKILL.md) will read next — write it for that purpose, not as a narrative transcript of the research process.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.