plan

Orchestrate research-driven planning workflows for complex .NET features.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill plan-dimsour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet-copilot/skills/plan
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill plan-dimsour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the planning phase of .NET development, offering a structured approach to task decomposition and research-driven orchestration, significantly reducing time and complexity for large features.

Core Features & Use Cases

  • Feature Planning: Provides a framework for decomposing features into actionable tasks and orchestrating research.
  • Research Orchestration: Leverages domain specialists to analyze and research codebase, offering a comprehensive plan.
  • Use Case: Ideal for planning complex .NET features that touch multiple modules or files, such as implementing a new API or UI component.

Quick Start

Create a detailed plan for your feature by using the /dotnet:plan command followed by a feature description or existing plan reference.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan complex .NET features that span multiple files and modules?

Planning complex .NET features requires research-driven task decomposition to break down multi-file development into structured, actionable tasks before coding begins. This approach orchestrates codebase analysis to ensure comprehensive preparation.

What is research-driven task decomposition for .NET development?

Research-driven task decomposition is a planning mechanism that leverages domain specialists to analyze your codebase, orchestrating a comprehensive breakdown of features into actionable tasks for complex .NET development.

Can I use this planning approach for implementing a new API or UI component?

Yes, this planning approach is ideal for implementing new APIs or UI components in .NET, providing a structured framework to decompose these complex features into actionable tasks through comprehensive codebase research.

How do I start planning a .NET feature using a feature description?

To start planning a .NET feature, use the command followed by your feature description or existing plan reference. This initiates the research-driven orchestration workflow to generate a detailed, actionable plan.

When should I use structured orchestration for .NET feature planning?

Use structured orchestration for .NET feature planning when facing complex, multi-file feature development, as it significantly reduces time and complexity by ensuring a comprehensive, well-researched planning process before coding.