mt-create-plan

Create structured GitHub Issue implementation plans from development ideas.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill mt-create-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt-create-plan
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-create-plan
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-create-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform vague development ideas into structured GitHub Issue based plans by guiding users through clarification, refinement, and planning decisions before execution.

Core Features & Use Cases

  • Interactive Plan Refinement: Conducts a structured questioning process to clarify goals, constraints, decisions, and completion criteria before creating a plan.
  • GitHub Issue Planning Workflow: Creates or updates plan Issues with labels, project integration, status management, and repository targeting rules.
  • Use Case: A developer with a feature idea can use this Skill to refine requirements into an approved draft plan Issue ready for implementation workflows.

Quick Start

Use the mt-create-plan skill to help me create and refine a GitHub Issue based implementation plan for my idea.

Frequently Asked Questions about mt-create-plan

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

FAQPage Schema
How do I turn a vague software idea into a structured GitHub Issue plan?

To turn a vague software idea into a structured GitHub Issue plan, this Skill guides you through an interactive refinement process that clarifies goals, constraints, and completion criteria before generating the issue.

What is the best way to refine project requirements before creating a GitHub Issue?

Refining project requirements before creating a GitHub Issue is best handled through structured questioning that clarifies decisions and completion criteria, ensuring you produce an approved draft plan ready for implementation workflows.

Do I need GitHub CLI workflows to manage issue planning and status transitions?

Yes, GitHub CLI workflows are required to manage issue planning, handle configuration files, apply plan templates, and execute status transitions between draft and refined planning states.

Can I use this workflow to add labels and project integration to draft plan issues?

Yes, you can use this GitHub Issue planning workflow to create or update plan issues with labels, project integration, status management, and repository targeting rules during the planning phase.

When should I not use an interactive plan refinement workflow for issue creation?

You should not use an interactive plan refinement workflow if your development idea is already fully refined, or if your project does not use GitHub Issues and CLI workflows for project management tracking.