plan-task-planner

Convert complex requirements into ordered execution plans with tasks and risk mitigations.

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill plan-task-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-task-planner
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/plan-task-planner
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill plan-task-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Task Planner converts complex requirements into a structured, ordered execution plan that reduces ambiguity and aligns teams on the path to delivery.

Core Features & Use Cases

  • Load minimal context (project scope and objectives) and route instructions to generate an ordered plan.
  • Produce an output contract: scope summary, ordered tasks, validation checklist, risk list, and delivery slices for incremental delivery.
  • Use cases include planning roadmaps, breakdowns for cross-domain initiatives, effort estimation, and governance for multi-step delivery.

Quick Start

Provide an execution plan with ordered tasks, validations, and risk mitigations for the requested project.

Frequently Asked Questions about plan-task-planner

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

FAQPage Schema
What is an execution plan in software engineering and when do I need one?

An execution plan converts complex requirements into a structured, ordered task list with validation checkpoints and risk mitigation. You need one when planning roadmaps, effort estimation, or cross-domain coordination to reduce ambiguity and align teams on delivery.

How do I break down complex software requirements into an ordered task list?

To break down complex requirements, provide your project scope, constraints, and acceptance criteria to generate a scoped task list. This process outputs ordered tasks, validation checkpoints, a risk list, and delivery slices for incremental execution.

What components do I need to create a roadmap and effort estimation for a software project?

Creating a roadmap and effort estimation requires defining your objective, constraints, assumptions, and acceptance criteria. These inputs generate a structured output contract containing ordered tasks, a validation checklist, a risk list, and delivery slices.

Can I use task planning for multi-step delivery and cross-domain coordination?

Task planning supports multi-step delivery and cross-domain coordination by converting complex requirements into structured execution strategies. It applies governance by generating ordered tasks, validation checkpoints, and incremental delivery slices for software projects.

What's the best way to structure risk mitigation and validation checkpoints for software execution?

The best way to structure risk mitigation is by providing project objectives and constraints to generate an output contract. This yields a scoped task list paired with a validation checklist and a dedicated risk list to ensure aligned, incremental delivery slices.