create-execplan

Create deterministic ExecPlan workflows with context packs and task tables.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adam-jackson-cf/enaible --skill create-execplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-execplan
Source: https://github.com/adam-jackson-cf/enaible/tree/main/.build/rendered/claude-code/skills/create-execplan
Command: npx skills add https://github.com/adam-jackson-cf/enaible --skill create-execplan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the creation of deterministic, auditable ExecPlan workflows for implementing code changes, enabling teams to plan with explicit context and verifiable steps.

Core Features & Use Cases

  • Two-artifact workflow: Context Pack + ExecPlan to separate orientation from execution steps.
  • Explicit task tables with file anchors and verification commands to guide low-reasoning executors.
  • Greenfield vs brownfield guidance to manage risks, traceability, and change scope in legacy or new codebases.
  • Living-document approach: artifacts evolve with clarifications, decisions, and evidence, ensuring replayable planning.

Quick Start

Run the scaffold script with a plan title to generate a context-pack and an execplan for the change.

Frequently Asked Questions about create-execplan

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

FAQPage Schema
How do I create deterministic execution plans for code changes?

You create deterministic execution plans by generating a two-artifact workflow: a Context Pack for orientation and an ExecPlan containing explicit task tables with file anchors and verification commands.

What is a Context Pack and how does it support change planning?

A Context Pack is an orientation artifact that captures explicit context, anchors, and clarifications for a planned code change, working alongside an ExecPlan to separate understanding the scope from defining the execution steps.

Can I use automated planning workflows for brownfield legacy codebases?

Yes, automated planning workflows support both greenfield and brownfield scenarios, with the generated ExecPlan providing specific guidance to manage risks, traceability, and change scope when modifying legacy codebases.

How do I ensure code change plans remain auditable as requirements evolve?

To ensure auditable change plans, use a living-document approach where Context Pack and ExecPlan artifacts evolve with clarifications, decisions, and evidence, ensuring the entire planning process remains replayable and traceable.

Does plan readiness governance require explicit verification commands?

Yes, plan readiness governance requires explicit verification commands, with the ExecPlan enforcing this by embedding verification commands and evidence traceability directly into task tables for low-reasoning executors.

What are the limitations of deterministic planning for code changes?

Deterministic planning relies on explicit context and file anchors, meaning it requires accurate upfront orientation and functions best when scope and verification criteria are clearly defined rather than for ambiguous, exploratory changes.