plan

Coordinate plan-create, plan-exec, and plan-status tasks with deterministic sequencing.

6|1|Updated Jan 5, 2026

Search Tags:#automation #markdown #orchestration #status #plan #task-management

Ready to run

npx skills add https://github.com/JordanGunn/skills --skill plan-jordangunn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/JordanGunn/skills/tree/main/skills/plan
Command: npx skills add https://github.com/JordanGunn/skills --skill plan-jordangunn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the creation, execution, and status tracking of a multi-skill plan, ensuring deterministic sequencing and clear integration points.

Core Features & Use Cases

Coordinates plan-create, plan-exec, and plan-status to form a cohesive planning workflow.
Provides safe, predictable dispatch and status visibility for complex task trees.
Use case: Orchestrate a root plan that creates sub-plans, runs tasks in order, and reports completion.

Quick Start

Instruct the agent to initialize a new planning phase and wire in the required sub-plans with defined inputs and outputs.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I orchestrate multi-step task execution with deterministic sequencing?▼

Multi-step task execution is orchestrated by coordinating plan-create, plan-exec, and plan-status phases. This enforces a frontmatter-driven schema with defined inputs, outputs, and dependencies to maintain a safe, predictable execution order for complex task trees.

What is the best way to track status visibility for complex planning workflows?▼

Status visibility for planning workflows is tracked by applying a frontmatter-driven schema and pipeline dependencies. This ensures deterministic sequencing across sub-plans, providing clear integration points and completion reporting for complex task trees.

How do I manage sub-plans and dependencies in markdown task management?▼

Sub-plans and dependencies are managed in markdown by enforcing a frontmatter-driven schema. This pipelines tasks in a predictable execution order, ensuring safe dispatch and clear inputs and outputs for each sub-plan.

Does this planning orchestration approach require specific dependencies or components?▼

No specific dependencies or components are required. The orchestration applies a frontmatter-driven schema directly to markdown workflows, coordinating plan creation, execution, and status tracking without external tooling prerequisites.

Can I audit plan execution order and task completion in a multi-skill workflow?▼

Plan execution order and task completion can be audited using the deterministic planning schema. By enforcing pipelines and dependencies across plan-create, plan-exec, and plan-status, the workflow maintains clear integration points for safe auditing.

When should I not use a deterministic orchestration schema for task management?▼

Deterministic orchestration should be avoided when task workflows lack clear inputs, outputs, or sequential dependencies. Without the need for predictable execution order and frontmatter-driven status visibility, simpler task management approaches are more suitable.