invoke-plan

Generate implementation plans from approved technical specifications via multiple planner agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ricky-russo/invoke --skill invoke-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoke-plan
Source: https://github.com/ricky-russo/invoke/tree/main/plugin/skills/invoke-plan
Command: npx skills add https://github.com/ricky-russo/invoke --skill invoke-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an approved specification into a concrete, reviewable implementation plan and coordinates planner agents to generate competing approaches so teams can choose and approve a clear path to implementation.

Core Features & Use Cases

  • Multi-planner dispatch: Run one or more planner agents across configured providers to produce competing implementation plans.
  • Plan comparison and synthesis: Aggregate planner outputs, highlight agreements and trade-offs, and synthesize hybrid plans when requested.
  • User-driven approval flow: Present plans, solicit a selection and explicit approval, support re-planning with additional constraints, and save the approved plan as a pipeline artifact.
  • Session-safe orchestration: Enforce session_id usage, poll batch status correctly, fetch task results only when terminal, and update pipeline state to advance to the next stage.
  • Use Case: Converting a reviewed spec into a detailed developer-facing plan that drives automated task breakdown and build orchestration.

Quick Start

Ask invoke-plan to dispatch planners for the approved spec, compare their outputs, and save the user‑approved plan.

Frequently Asked Questions about invoke-plan

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

FAQPage Schema
How do I generate an implementation plan from an approved technical specification?

To generate an implementation plan from an approved technical specification, you can dispatch multiple planner agents to produce competing approaches, compare their outputs, and save the user-approved plan as a pipeline artifact.

Can I run multiple planner agents to compare competing implementation approaches?

Yes, you can run multiple planner agents across configured providers to produce competing implementation approaches, aggregate their outputs, highlight trade-offs, and synthesize hybrid plans for user selection.

What is the best way to orchestrate a multi-provider planning pipeline for software specs?

The best way to orchestrate a multi-provider planning pipeline is to enforce session-bound tool calls, dispatch planner agents, poll batch status until terminal, fetch task results, and update pipeline state to advance stages.

How does the plan comparison and synthesis process work for competing agent outputs?

The plan comparison process works by aggregating outputs from dispatched planner agents, highlighting agreements and trade-offs between competing approaches, and synthesizing hybrid plans when requested before user approval.

Does the planning orchestration handle planner agent failures during task execution?

Yes, the planning orchestration handles planner failures by enforcing session-safe tool calls, polling batch status correctly, and fetching task results only when they reach a terminal state to maintain pipeline integrity.

When do I need a user-driven approval flow for implementation plans?

You need a user-driven approval flow when converting reviewed specs into developer-facing plans, requiring explicit selection and approval before saving the finalized plan as a standardized pipeline artifact.