plan-draft-all-core

Coordinate planning stages 1 through 4 and produce a consolidated supervisor report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KGmufassa/Escrolly --skill plan-draft-all-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-draft-all-core
Source: https://github.com/KGmufassa/Escrolly/tree/main/.opencode/skills/plan-draft-all-core
Command: npx skills add https://github.com/KGmufassa/Escrolly --skill plan-draft-all-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supervises the full planning flow by reusing the combined stage contracts in order, generating a consolidated supervisor report, and stopping on the first failure to prevent cascading errors.

Core Features & Use Cases

  • Orchestrates plan-stage1 through plan-stage4 in sequence without bypassing stage logic.
  • Reuses the stage command contracts to ensure consistent behavior across stages.
  • Writes consolidated supervisor reports to Build Plan/Active Plans and updates related JSON manifests and state.
  • Produces an auditable trail of completed and blocked stages for post-mortem analysis.
  • Use Case: run the full pipeline to obtain a single summary report and robust failure handling.

Quick Start

Run plan-stage1, plan-stage2, plan-stage3, and plan-stage4 in order, then review the consolidated supervisor report.

Frequently Asked Questions about plan-draft-all-core

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

FAQPage Schema
How do I automate end-to-end planning workflows across multiple stages?

To automate end-to-end planning workflows, you can orchestrate plan-stage1 through plan-stage4 in sequence. This ensures consistent behavior by reusing stage command contracts and produces a unified supervisor report summarizing the results.

What is the best way to consolidate planning reports from different pipeline stages?

The best way to consolidate planning reports is to run an orchestrated planning pipeline that executes stages 1 through 4. It generates a single unified supervisor report and automatically updates manifest.json and state.json files.

Why does my planning pipeline stop executing before reaching the final stage?

Your planning pipeline stops executing because it is designed to halt on the first failure. This prevents cascading errors and produces an auditable trail of completed and blocked stages for post-mortem analysis.

Can I run individual stage contracts without bypassing the core planning logic?

Yes, you can run individual stage contracts without bypassing core planning logic. The orchestration pipeline integrates stage logic sequentially from stage 1 to 4, ensuring no individual stage contract is skipped or bypassed.

Do I need to manually update state.json after running a full planning workflow?

No, you do not need to manually update state.json after running a full planning workflow. The orchestration pipeline automatically updates manifest.json and state.json while writing consolidated supervisor reports to Build Plan and Active Plans.