plan-research

Resolve planning topic scope and write structured RESEARCH.md files.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-research
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/plan-research
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve scope for planning topics and produce RESEARCH.md artifacts that downstream planning skills consume.

Core Features & Use Cases

  • Guides discovery of valid planning phases or topics and writes RESEARCH.md to .planning/research/<slug>.
  • Integrates with existing planning artifacts such as ROADMAP.md, CONTEXT.md, and REQUIREMENTS.md to maintain context.
  • Supports orchestration for iterative research by spawning a dedicated subagent when deeper analysis is needed.

Quick Start

Instruct the agent to initialize and save a new RESEARCH.md for a target phase or topic under .planning/research.

Frequently Asked Questions about plan-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research scope for a planning topic before writing a plan?

To research scope for a planning topic, you can resolve scope and generate a structured RESEARCH.md file under .planning/research/<slug>. This artifact guides downstream planning and review processes by capturing context before implementation.

What is a RESEARCH.md file used for in a planning workflow?

A RESEARCH.md file is used to document resolved scope and research context for specific planning phases. It serves as an input artifact for downstream planning skills to consume when generating implementation plans.

Can I use existing ROADMAP.md and REQUIREMENTS.md files when generating research context?

Yes, the research workflow integrates existing planning artifacts such as ROADMAP.md, CONTEXT.md, and REQUIREMENTS.md. It references these files to maintain context and ensure the generated RESEARCH.md aligns with current project scope.

How to handle deep analysis during planning research without losing context?

To handle deep analysis during planning research, the workflow can spawn a dedicated subagent for iterative research. This subagent coordinates research context and enforces guardrails while exploring complex topics.

Does the research planning workflow write implementation code or plan files?

No, the research planning workflow does not write a PLAN.md or implementation code unless explicitly requested. It strictly produces RESEARCH.md artifacts to guide downstream planning and review phases.

When do I need to generate a research artifact before creating a project plan?

You need to generate a research artifact before creating a project plan when you must resolve ambiguous scope for specific phases. Producing a RESEARCH.md ensures downstream planning skills have structured context to validate against guardrails.