agentic-plan-crafting

Create an executable planning document with task sequencing and verification.

3|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-plan-crafting-alphabeen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-plan-crafting
Source: https://github.com/alphabeen/oh-my-jinho/tree/main/skills/agentic-plan-crafting
Command: npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-plan-crafting-alphabeen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a clearly defined work scope into an executable plan that can be carried out by a worker with no codebase context, enabling fast, deterministic planning.

Core Features & Use Cases

  • Executable plan generation: Produces a plan that can be executed step-by-step by a worker without further questions.
  • Parallelizable worker-validator model: Supports spawning independent task validators to accelerate execution.
  • Self-review guardrails: Enforces self-review and clear task boundaries to minimize drift and conflicts.

Quick Start

Provide a clearly defined context brief and request a plan to generate an actionable, decomposed plan.

Frequently Asked Questions about agentic-plan-crafting

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

FAQPage Schema
How do I create an executable plan from a defined work scope?

To create an executable plan from a defined work scope, provide a clear context brief to generate a decomposed plan with concrete steps, verifiable outcomes, and a built-in verification strategy.

What is a parallelizable worker-validator model for task decomposition?

A parallelizable worker-validator model decomposes tasks into independent sequences, spawning separate task validators to accelerate execution while enforcing self-review guardrails to minimize drift and conflicts.

Does executable plan generation require prior codebase context for the worker?

No, executable plan generation produces a step-by-step document designed to be executed by a worker without any prior codebase context, enabling fast and deterministic planning execution.

What's the best way to structure task sequencing and dependencies for multi-step workflows?

The best way to structure task sequencing and dependencies for multi-step workflows is generating a plan with explicit steps, parallelizable execution paths, and self-review guardrails to close the plan.

Why does task execution drift from the original planning document?

Task execution drifts from the original planning document due to unclear task boundaries, which is mitigated by enforcing self-review guardrails and specifying verifiable outcomes during plan generation.