planner-agent

Convert architecture and PRDs into sequenced task lists with dependencies.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill planner-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-agent
Source: https://github.com/unnamedmistress/menuspy-marketing/tree/main/planner-agent
Command: npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill planner-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts architecture and PRDs into actionable, sequenced task lists with clear dependencies, enabling teams to translate high-level plans into executable work.

Core Features & Use Cases

  • Breaks down architecture and PRDs into structured task hierarchies with dependencies.
  • Produces sequenced implementation steps and estimated complexity per task.
  • Suitable for product planning, sprint scoping, and feature delivery roadmaps.

Quick Start

Provide the architecture and PRD, then request a prioritized, dependency-aware task list.

Frequently Asked Questions about planner-agent

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

FAQPage Schema
How do I convert a PRD and architecture into an actionable build plan?

Task breakdown structures implementations by generating a sequenced task hierarchy with clear dependencies. It tags task types like backend, frontend, tests, devops, and docs to ensure structured sprint scoping and feature delivery.

What is the best way to sequence implementation steps for sprint planning?

The best way to sequence implementation steps for sprint planning is to generate a dependency-aware task list from your architecture. This provides clear task sequences, complexity estimates, and specific task type tags for executable work.

Can I use architecture documents for sprint scoping and feature breakdown?

Yes, you can use architecture documents for sprint scoping and feature breakdown by converting them into structured task hierarchies. This process produces dependency-aware implementation steps suitable for product planning and delivery roadmaps.

Do I need a complete PRD to generate a dependency-aware task list?

A complete PRD is needed to generate a dependency-aware task list because the breakdown relies on both architecture and product requirements. Providing detailed documents ensures accurate task sequencing and complexity estimates.

What task types are supported when breaking down architecture into a build plan?

Supported task types when breaking down architecture include backend, frontend, tests, devops, and docs. Tagging these task types within the dependency-aware task list ensures clear categorization for executable work.