subtask-planning

Generate phased implementation plans with DAG dependencies and verification steps.

Updated Jan 17, 2026

Search Tags:#workflow #planning #dependencies #decomposition #phases #subtasks

Ready to run

npx skills add https://github.com/meetpradeepp/agentic_migration --skill subtask-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subtask-planning
Source: https://github.com/meetpradeepp/agentic_migration/tree/main/.github/skills/subtask-planning
Command: npx skills add https://github.com/meetpradeepp/agentic_migration --skill subtask-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subtask Planning helps teams translate vague requirements into concrete, auditable work items by decomposing work into phases, subtasks, and dependencies.

Core Features & Use Cases

Phase-based decomposition that enforces a mandatory INVESTIGATION phase and DAG dependencies.
One-service-per-subtask with a 1-3 file limit to keep tasks focused and reviewable.
Automatic generation of detailed verification steps, risk notes, and cross-service boundaries.
Real-world use: a migration or refactor is broken down into executable steps that can be handed to implementation and QA.

Quick Start

Use this skill to generate a multi-phase implementation plan from a high-level specification, ensuring each subtask targets a single service, references 1-3 files, and includes explicit dependencies and verification steps.

Frequently Asked Questions about subtask-planning

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

FAQPage Schema

How do I decompose a multi-service migration into phased subtasks with dependencies?▼

Multi-service migration decomposition breaks work into phased subtasks by enforcing a mandatory investigation phase, mapping explicit DAG dependencies, and restricting each subtask to a single service for a structured implementation plan.

What is the best way to generate an implementation plan for a complex software refactor?▼

Generating an implementation plan for a complex refactor involves decomposing work into focused subtasks limited to 1-3 files each, producing dependency graphs, risk notes, and detailed verification steps for QA.

Can I use subtask planning for cross-service architecture investigations?▼

Yes, subtask planning applies to cross-service architecture investigations by initiating a mandatory investigation phase, generating auditable work items with explicit dependencies and cross-service boundaries.

How do I structure verification steps and entry criteria for feature implementation?▼

Structuring verification steps for feature implementation requires defining entry and exit criteria for each subtask, outputting detailed verification steps, risk notes, and cross-service boundaries to ensure auditable execution.

Why should I limit task decomposition to one service and 1-3 files per subtask?▼

Limiting task decomposition to one service and 1-3 files per subtask keeps work items focused and reviewable, preventing sprawling changes and ensuring each task within the dependency DAG remains auditable.