plan-adhoc

Generate executable runbooks for weak orchestrator agents using a four-point planning process.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/agent-core --skill plan-adhoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-adhoc
Source: https://github.com/ddaanet/agent-core/tree/main/skills/plan-adhoc
Command: npx skills add https://github.com/ddaanet/agent-core --skill plan-adhoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams transform high-level tasks into detailed, executable runbooks for weak orchestrator agents using a formal four-point planning process.

Core Features & Use Cases

  • Generate end-to-end runbooks that map planning decisions to concrete steps for haiku/sonnet/opus agents
  • Produce artifacts and orchestrator plans with automated validation to ensure traceability
  • Enable cross-project runbook design, review, and handoff to execution

Quick Start

Invoke the plan-adhoc skill to begin runbook planning for a given task with a single command, then follow the guided workflow to produce artifacts and hand off for execution.

Frequently Asked Questions about plan-adhoc

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

FAQPage Schema
How do I turn complex software tasks into executable runbooks?▼

Executable runbooks are built using a structured four-point planning process that maps high-level tasks to concrete steps for orchestrator agents. This ensures strict file-path conventions and model assignments are applied during preparation.

What is the best way to generate orchestrator plans for weak agents?▼

Generating orchestrator plans for weak agents requires producing artifacts with automated validation to ensure traceability. A formal planning process maps decisions directly to haiku, sonnet, or opus model assignments for execution.

How does the four-point planning process work for runbook design?▼

The four-point planning process works by transforming high-level tasks into detailed, executable runbooks. It enforces governance, clear execution criteria, and automated validation to ensure traceability across software projects.

Can I use this runbook design approach for cross-project automation workflows?▼

Yes, this runbook design approach supports cross-project automation workflows by enabling end-to-end runbook design, review, and handoff to execution. It applies to planning and design tasks requiring explicit runbook artifacts.

Do I need specific dependencies to start runbook planning?▼

No specific dependencies are required to start runbook planning. You invoke the skill with a single command and follow the guided workflow to produce artifacts and hand off the generated orchestrator plans for execution.

When should I not use a structured runbook for task orchestration?▼

Structured runbooks are not necessary for simple, ad-hoc tasks that lack explicit governance or artifact generation requirements. They are designed for complex software projects needing strict file-path conventions and clear execution criteria.