planning-research

Translate technical research into phased implementation plans with dependencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/siriwatknp/jun-cc --skill planning-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-research
Source: https://github.com/siriwatknp/jun-cc/tree/main/skills/planning-research
Command: npx skills add https://github.com/siriwatknp/jun-cc --skill planning-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates technical research and analysis into a clear, phased implementation plan that engineers can execute, eliminating ambiguity and ensuring traceable progress.

Core Features & Use Cases

  • Structured Phases: Breaks work into sequential, dependency-aware phases with defined scope and measurable outcomes.
  • Plan Revision: Updates an existing plan when underlying analysis changes, preserving history and ensuring alignment with new findings.
  • Automated Plan Location: Defaults to the path .claude/tasks/<dd-mm-yyyy>-<short-description>/plan.md in the current directory, with support for custom paths when provided.
  • Use Case: When you have a new technical analysis document, generate a concrete task backlog that engineers can start implementing immediately.

Quick Start

Create a new plan for your current project or revise an existing plan by providing the analysis reference and desired date. The skill will output a plan markdown file at the default location (or a specified path) with numbered, testable phases and dependency ordering.

Frequently Asked Questions about planning-research

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

FAQPage Schema
How do I translate technical research into executable software engineering tasks?

To translate technical research into executable tasks, this Skill generates a structured, phased implementation plan with dependency-aware scopes and measurable outcomes. It converts analysis documents into a concrete task backlog that engineers can start implementing immediately.

What is the best way to structure implementation plans into phased development tasks?

Structuring implementation plans into phased development tasks involves breaking work into sequential, dependency-aware phases with defined scope and measurable outcomes. This Skill automates that process, ensuring traceable progress and eliminating ambiguity for engineers.

How do I update an existing implementation plan when underlying technical analysis changes?

To update an existing implementation plan when technical analysis changes, this Skill applies a plan revision workflow. It updates the plan while preserving history and ensuring alignment with new findings from the updated analysis.

Where does the generated implementation plan markdown file get saved by default?

The generated implementation plan markdown file defaults to the path .claude/tasks/<dd-mm-yyyy>-<short-description>/plan.md in the current directory. You can also specify a custom output path when generating or revising the plan.

Can I generate a task backlog from a technical analysis document for immediate development?

Yes, you can generate a concrete task backlog from a technical analysis document for immediate development. By providing the analysis reference and desired date, the Skill outputs a plan with numbered, testable phases and dependency ordering.

Do I need any specific dependencies to create dependency-aware implementation plans?

No specific dependencies are required to create dependency-aware implementation plans. The Skill operates independently to translate technical research and analysis into a clear, phased plan that engineers can execute without external tools.