planner

Generate a 13-element planning contract from a discovery artifact.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/espensev/ai-skills --skill planner-espensev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/espensev/ai-skills/tree/main/gemini-skills/skills/planner
Command: npx skills add https://github.com/espensev/ai-skills --skill planner-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Planner Agent transforms discovery results into a formal planning contract that guides downstream execution, reducing ambiguity and handoff risk.

Core Features & Use Cases

  • Produces a definitive planning contract (docs/planning-contract.md) from a discovery artifact.
  • Enforces a 13-element handoff structure to ensure complete, executable plans.
  • Guards writes to the planning artifact and requires the discovery artifact (docs/system-map.md) for traceability.

Quick Start

Provide the discovery artifact and allow the Planner to generate docs/planning-contract.md.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I generate a formal planning contract from a system map for multi-agent orchestration?

To generate a planning contract, you provide the discovery artifact docs/system-map.md and let the planner synthesize strategy and repository insights into docs/planning-contract.md following a fixed 13-element structure.

What is a planning contract in multi-agent orchestration and when do I need one?

A planning contract is a formal handoff document that transforms discovery results into an executable plan, reducing ambiguity and handoff risk in multi-agent orchestration projects. You need one when synthesizing strategy from system maps.

Do I need a system-map.md file before creating a planning contract?

Yes, you need the docs/system-map.md discovery artifact as a required input. The planner enforces traceability by guarding writes and requiring this discovery artifact to produce the formal planning contract.

What's the best way to structure a multi-agent handoff document to reduce execution risk?

The best way to structure a multi-agent handoff document is using a fixed 13-element structure that enforces complete, executable plans. This formal planning contract reduces ambiguity and downstream execution risk.

Why does multi-agent planning fail without a formal discovery-to-execution contract?

Multi-agent planning fails without a formal contract due to ambiguity and handoff risk between discovery and execution. A fixed 13-element planning contract ensures complete, executable plans synthesized from system maps.