planner

Decompose tasks into actionable subtasks for user review and NoteCove creation.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/gara2000/agentmesh --skill planner-gara2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/gara2000/agentmesh/tree/main/plugins/agentic-workflows/skills/planner
Command: npx skills add https://github.com/gara2000/agentmesh --skill planner-gara2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planner orchestrates the decomposition of a marked task by proposing subtasks for user review and, upon approval, creates them as NoteCove children of the parent task, streamlining planning and handoffs.

Core Features & Use Cases

  • Receives a task designated for decomposition and proposes concrete subtasks for review.
  • Creates approved subtasks as children of the parent task in NoteCove, preserving context and traceability.
  • Uses multi-phase signaling (Attention, doing, done) and per-session resume logic to coordinate with an orchestrator.

Quick Start

Provide the task slug and project key to initiate the decomposition workflow.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I decompose a workflow task into actionable subtasks?

Task decomposition splits a marked task into actionable subtasks for user review, generating them as NoteCove children of the parent task to preserve context and traceability.

How does task decomposition coordinate with a workflow orchestrator?

Task decomposition coordinates with an orchestrator using multi-phase signaling, including Attention, doing, and done phases, alongside per-session resume logic to manage task state and handoffs.

Do I need NoteCove to manage subtask creation and logging?

Yes, task decomposition relies on NoteCove commands to create approved subtasks as children of the parent task, while also using its signaling loop to manage task state, logging, and error handling.

What is required to start the task decomposition workflow?

To initiate the task decomposition workflow, you must provide the task slug and project key, which triggers the orchestrator to mark the task and require Attention signaling before subtasks are created.

What happens if an error occurs during subtask creation?

Errors during subtask creation are managed through the signaling loop, which handles task state logging and error resolution to ensure the workflow can resume correctly per-session.