plan-to-invoker

Convert plans into validated Invoker YAML workflow files for DAG-based task orchestration.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill plan-to-invoker-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-to-invoker
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/plan-to-invoker
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill plan-to-invoker-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a written plan or conversation into a runnable Invoker workflow requires strict YAML structure, review-compression headings, layered decomposition metadata, and deterministic validation — doing this by hand produces plans that fail submission gates or silently drop work. ## Core Features & Use Cases - Plan-to-YAML conversion: Transforms Markdown plans, conversations, or policy documents into Invoker YAML plans with required top-level fields (name, onFinish, mergeMode, repoUrl or scratch, tasks). - Deterministic validation gate: Runs skill-doctor.sh plus completeness, atomicity, coverage-map, and stack-manifest checks so plans pass schema, zero-context prompt, and review-unit requirements before submission. - Stack-first and formula-first authoring: Splits multi-slice implementations into chained workflow YAML files and renders proven formula templates (bugfix, entity-research) instead of hand-authoring shapes. - Use Case: Given a feature plan for a multi-package refactor, generate a stack of step-N workflow YAML files, validate them with skill-doctor, and submit the head workflow for review before fan-out. ## Quick Start Ask the agent to convert your plan into an Invoker plan, for example: convert this plan to invoker and validate it before submission.

Frequently Asked Questions about plan-to-invoker

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

FAQPage Schema
How do I convert a plan into an Invoker YAML workflow?

Write or paste your plan, then trigger the skill with phrases like "convert to invoker" or "submit to invoker". It produces a Markdown handoff, converts it to YAML with required fields (name, onFinish, mergeMode, repoUrl, tasks), and validates it with skill-doctor.sh before submission.

What validation does an Invoker plan need before submission?

Run bash skills/plan-to-invoker/scripts/skill-doctor.sh <plan-file> as the primary gate. It runs assumption extraction, verify-plan generation, YAML schema validation, strict atomicity linting, and parse-results checks in one command with pass/fail exit codes.

When should a plan be split into multiple Invoker workflows?

Split when the implementation has more than one review slice, layer, conceptual unit, or PR-worthy commit. Author multiple step-N YAML files and submit them with submit-workflow-chain.sh, wiring later workflows to the previous merge gate via externalDependencies.

Why does skill-doctor reject my Invoker plan?

Common causes include missing Goal/Motivation/Safety invariant headings, leftover REPLACE_ME placeholders, missing repoUrl without scratch: true, non-runnable Verify commands, unsupported green-baseline claims, or prompt tasks lacking Files/Change types/Acceptance criteria sections.

Can I generate an Invoker plan without submitting it?

Yes. Benchmark or direct-output mode writes the final YAML to a specified absolute path without scanning the repo, running validation loops, or submitting. The file must start with top-level name and include onFinish, mergeMode, repoUrl or scratch, and tasks.