planner-agent

Decompose goals into bounded work units with scope, sequencing, and acceptance criteria.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/harkers/forge-email-server --skill planner-agent-harkers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-agent
Source: https://github.com/harkers/forge-email-server/tree/main/skills/planner-agent
Command: npx skills add https://github.com/harkers/forge-email-server --skill planner-agent-harkers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planner Agent helps teams break goals into bounded work units with defined scope, sequencing, dependencies, acceptance criteria, and stop conditions to reduce ambiguity before execution.

Core Features & Use Cases

  • Decompose goals into bounded units with ownership and sequencing
  • Define dependencies, acceptance criteria, and stop conditions
  • Apply a planning standard (objective, owner type, allowed/forbidden scope, expected outputs, validation checks)
  • Facilitate handoff of plans back to a manager or assigned worker

Quick Start

Decompose a complex goal into a single bounded work unit with clear scope, owner, and acceptance criteria.

Frequently Asked Questions about planner-agent

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

FAQPage Schema
How do I decompose a complex project goal into actionable work units?

Decomposing a complex project goal involves breaking it into bounded work units with clear scope, sequencing, dependencies, acceptance criteria, and stop conditions to reduce ambiguity before execution.

What is the best way to define acceptance criteria and stop conditions for milestones?

Defining acceptance criteria and stop conditions for milestones requires applying a planning standard that specifies the objective, owner type, allowed and forbidden scope, expected outputs, and validation checks for each unit.

How does work decomposition handle sequencing and dependencies for software projects?

Work decomposition handles sequencing and dependencies by defining bounded units with explicit ownership and execution order, facilitating safe work slicing and structured handoff back to a manager or assigned worker.

Can I use this planning approach for both software projects and operations tasks?

You can use this planning approach for both software projects and operations tasks, as it decomposes goals into bounded work units applicable to planning complex tasks, milestones, and safe work slicing before execution.

What planning standard is applied to ensure safe work slicing before execution?

The planning standard applied to ensure safe work slicing requires defining the objective, owner type, allowed and forbidden scope, expected outputs, validation checks, and stop conditions for each work unit.