plan

Generate checklist-style implementation plans from research.md files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill plan-jyhthegreat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/JYHTHEGREAT/jyh-system/tree/main/skills/plan
Command: npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill plan-jyhthegreat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms exploratory research and notes into a clear, checklist-style implementation plan so teams can move from analysis to execution without ambiguity or missed steps.

Core Features & Use Cases

  • Checklist generation: Converts research.md content into plan.md with step-by-step tasks and acceptance criteria.
  • Context-aware planning: References outputs from prior research runs to include relevant decisions and evidence.
  • Use Case: When handed a feature research document, produce a prioritized implementation checklist that developers can follow and verify against tests.

Quick Start

Generate a plan.md checklist from the existing research.md to produce actionable tasks and acceptance criteria.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn research notes into an actionable implementation checklist?

To turn research notes into an implementation checklist, you need a tool that parses research.md files and generates a plan.md with step-by-step tasks and acceptance criteria. This process maps your analysis directly to executable development steps.

What is the best way to generate a development plan from a research.md file?

Generating a development plan from a research.md file involves converting requirements and design notes into a prioritized checklist. The output plan.md maps specific tasks to acceptance criteria, ensuring developers can follow and verify implementation against tests.

Does the generated implementation plan include acceptance criteria for software tasks?

Yes, the generated implementation plan includes acceptance criteria for software tasks. It converts exploratory research and notes into a checklist-style plan.md that maps tasks directly to their verification requirements, preventing ambiguity during execution.

Can I create a broader scope implementation plan for complex engineering tasks?

You can create a broader scope implementation plan for complex engineering tasks by applying an optional master flag. This expands the checklist generation to cover a wider range of development requests when handling larger software features.

How does context-aware planning work with prior research outputs?

Context-aware planning works by referencing outputs from prior research runs to include relevant decisions and evidence. It ensures your generated checklist aligns with existing analysis, maintaining continuity from research to software execution.