skills.rest
Dunc4nJ
Dunc4nJCOMMUNITY
Explore all skills by this author →
GitHub

create-plan

Guide discovery and clarification to generate structured implementation plans.

1|Updated Jan 9, 2026
Search Tags:#planning#templates#clarification#handoff#exploration#software-development#plan-generation
One-click install
npx skills add https://github.com/Dunc4nJ/entropy-plugins --skill create-plan-dunc4nj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/Dunc4nJ/entropy-plugins/tree/main/create-plan/skills/create-plan
Command: npx skills add https://github.com/Dunc4nJ/entropy-plugins --skill create-plan-dunc4nj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams transform vague requests into concrete, executable implementation plans by guiding discovery, asking clarifying questions, and producing a structured plan document.

Core Features & Use Cases

  • End-to-end plan generation: exploration, clarification rounds, options, and a final plan artifact.
  • Phase-based templates: context, decisions, implementation steps, risks, dependencies, and verification criteria.
  • Handoff-ready artifacts: plan is self-contained and ready for developer execution.

Quick Start

Ask me to generate a plan for a feature, refactor, or system change and I will deliver a complete, executable plan.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I generate an executable implementation plan for a feature refactor?▼

To generate an executable implementation plan, you guide discovery through exploration and clarification rounds, producing a final artifact containing context, design decisions, implementation steps, dependencies, and verification criteria for developer handoff.

What is the best way to structure a handoff-ready plan for system changes?▼

A handoff-ready plan for system changes is structured using phase-based templates that document context, decisions, implementation steps, risks, dependencies, and verification criteria into a complete, self-contained artifact for developer execution.

How does the clarification process work when planning software development tasks?▼

The clarification process works by guiding discovery through targeted rounds of questions, exploring the codebase to generate options, and resolving ambiguities before formalizing the final implementation strategy for feature development.

Can I use this planning approach for both new features and codebase refactoring?▼

Yes, you can use this planning approach for both new features and codebase refactoring, as it applies to planning tasks across any system changes by transforming vague requests into concrete, executable implementation strategies.

What should be included in a feature development plan to ensure it is executable?▼

An executable feature development plan should include context, design decisions, step-by-step implementation instructions, dependencies, risk assessments, and verification criteria, ensuring the artifact is completely self-contained and ready for execution.

Related Skills

Explore More Software Engineering Skills→
tmdgusyatmdgusya
273

agentic-clarification

Resolve vague user requests through structured clarification and parallel codebase exploration.

Community
Advanced
AnastasiyaWAnastasiyaW
140

plan-to-tickets

Decompose project plans into Markdown tickets with acceptance criteria.

Community
Intermediate
marcuskroghmarcuskrogh

bug

Generate structured BUG.md files with repro steps and acceptance criteria.

Community
Intermediate
MarcoAntoliniMarcoAntolini
1

to-prd

Convert conversation context into a Product Requirements Document and integrate it into an issue tracker.

Community
Advanced