plan-orchestrable-steps

Decomposes a story into independently orchestrable implementation steps with interactive planner feedback.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill plan-orchestrable-steps-williamthorsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-orchestrable-steps
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/plan-orchestrable-steps
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill plan-orchestrable-steps-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a large story or task into parallelizable implementation steps is error-prone when done ad hoc, and plans often miss dependencies or unresolved questions. This Skill delegates decomposition to a planner subagent and refines the result through an interactive feedback loop before orchestration begins. ## Core Features & Use Cases - Planner delegation: Invokes a planner subagent to analyze the codebase and produce a machine-readable orchestration-plan.json plus timestamped Markdown snapshots. - Interactive refinement loop: Presents steps, dependency graphs, risks, and open questions, then re-invokes the planner with user feedback until approval. - Ticket-level artifacts: Stores the mutable plan JSON at the ticket level so it can be shared across later orchestration runs. - Use Case: Given a feature story like "add OAuth login", produce a step-by-step plan showing which steps run in parallel, which are sequential, and what questions remain, then hand it off to orchestrate-dev. ## Quick Start Ask the agent to break your story or task description into independently orchestrable implementation steps using the plan-orchestrable-steps skill.

Frequently Asked Questions about plan-orchestrable-steps

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

FAQPage Schema
How do I break a story into implementation steps for orchestration?▼

Provide the story or task description as the argument. The skill delegates codebase analysis to a planner subagent, which writes a machine-readable orchestration-plan.json and a timestamped Markdown plan for review.

How does the plan feedback loop work?▼

After the plan is presented, you can answer open questions, request changes to step scope or ordering, or approve. Feedback triggers a planner re-invocation that overwrites orchestration-plan.json and creates a new timestamped Markdown snapshot.

Where are orchestration plan artifacts stored?▼

Artifacts live at the ticket level under {artifact_base_dir}/projects/{project_slug}/tickets/{ticket_id}/. The mutable orchestration-plan.json is overwritten each iteration, while timestamped Markdown files preserve versioned snapshots.

Does this skill execute the plan after approval?▼

No. The skill only produces and finalizes the plan. Execution is handled separately by invoking orchestrate-dev once the user confirms the plan is ready.

What happens if no ticket ID exists for the plan?▼

The skill auto-generates a ticket ID in the format {YYYYMMDD}-{4 random hex} when the session context does not provide one, then creates the artifact directory before invoking the planner.