execplan-create

To turn a decided refactor into a structured planning document, the Skill reads decision artifacts and meta.json to draft a self-contained ExecPlan. It writes the resolved scope, artifacts, and milestones directly to the repository work-item path.

Generating an executable plan from a work item decision involves enforcing PLANS.md as the source of truth and reading active decisions. This process produces a novice-friendly plan document detailing scope and milestones within the repository structure.

To create a planning document for a decided PRD without missing scope boundaries, the Skill enforces PLANS.md as the source of truth. It reads the decision artifacts to preserve planning boundaries and writes the plan to the work-item path.

Yes, you can draft a self-contained execution plan that novices can follow. The Skill ensures the generated plan document is complete and self-contained, writing resolved scope, artifacts, and milestones to the repository work-item directory.

When converting a work item decision, the execution plan file should be stored at the .agent/work/<id-slug>/execplan.md path. This ensures the planning document remains organized within the repository work-item structure.

Yes, you need PLANS.md to generate a detailed plan from a problem statement. The Skill enforces PLANS.md as the source of truth and uses it alongside decision artifacts to draft the complete execution plan with updated metadata.