plan

Converts a software project specification into a dependency-aware task blueprint with ordered subtasks.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill plan-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/plan
Command: npx skills add https://github.com/arbazkhan971/godmode --skill plan-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms a project specification into a dependency-aware task blueprint that is ready for implementation.

Core Features & Use Cases

  • Decomposes specs into discrete tasks with IDs, titles, and file lists.
  • Builds a topological dependency graph to optimize parallel work and prevent cycles.
  • Use case: a product manager inputs a spec and receives an ordered plan for engineers, QA, and docs.

Quick Start

Feed the spec and output a topologically sorted list of tasks with IDs, titles, dependencies, and required files.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose a software specification into an ordered task list?

To decompose a software specification into an ordered task list, feed the spec into the planner to generate discrete tasks with IDs, titles, dependencies, and required files in a topologically sorted sequence.

What is a topological dependency graph for software task planning?

A topological dependency graph for software task planning is a directed structure that maps task prerequisites to optimize parallel work and prevent circular dependencies during implementation.

How do I structure engineering tasks to avoid circular dependencies?

To structure engineering tasks and avoid circular dependencies, the planner enforces constraints by building a topological graph that orders tasks sequentially and prevents cycles before implementation begins.

What are the file limits when decomposing a project specification?

When decomposing a project specification, the planner enforces strict file limits by allowing a maximum of 5 files per task and requiring exactly one task per file.

Can I plan tasks for both UI and API components from a single spec?

Yes, you can plan tasks for both UI and API components from a single spec, as the planner decomposes specifications across data, API, UI, config, and test layers into an executable blueprint.

Why does task decomposition enforce one task per file?

Task decomposition enforces one task per file to maintain strict boundaries, ensuring tasks remain granular, manageable for engineers and QA, and aligned with the topological dependency graph.