plan-work

Convert approved designs into structured implementation plans with required sections.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/bcbeidel/toolkit --skill plan-work-bcbeidel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/work/skills/plan-work
Command: npx skills add https://github.com/bcbeidel/toolkit --skill plan-work-bcbeidel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plans often lag behind designs, causing drift and rework. This skill converts approved designs or requirements into structured implementation plans with explicit lifecycle management and verification criteria.

Core Features & Use Cases

  • Create a step-by-step implementation plan from a design document or feature description.
  • Enforce required sections (Goal, Scope, Approach, File Changes, Tasks, Validation) and 6 required sections per Plan Template.
  • Generate a reusable plan artifact that is actionable, version-controlled, and reviewable.

Quick Start

Provide the design doc path or feature description to generate a complete plan ready for review.

Frequently Asked Questions about plan-work

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

FAQPage Schema
How do I create an implementation plan from a design document?

To create an implementation plan from a design document, provide the design doc path or feature description to generate a structured plan. The plan enforces required sections like Goal, Scope, Approach, File Changes, Tasks, and Validation to ensure verifiable execution.

What is the best way to prevent plan drift from approved designs?

Preventing plan drift from approved designs requires enforcing traceability to design docs within a structured plan format. This approach converts designs into version-controlled plan artifacts stored in a designated .plans/ folder with branch and PR metadata for lifecycle management.

How does task scoping and assignment work with a structured plan document?

Task scoping and assignment within a structured plan document works by transforming requirements into explicit tasks with required sections. The generated artifact is actionable, version-controlled, and reviewable, ensuring traceability to design docs while managing the implementation lifecycle.

Can I use frontmatter and branch metadata in a verifiable plan template?

Yes, you can use frontmatter and branch metadata in a verifiable plan template. The generated plan document supports frontmatter and stores results in a designated .plans/ folder with branch and PR metadata for version control and lifecycle management.

What required sections are enforced when converting requirements into a plan artifact?

When converting requirements into a plan artifact, the Plan Document Format enforces six required sections: Goal, Scope, Approach, File Changes, Tasks, and Validation. These sections ensure the generated plan is verifiable, actionable, and traceable to the original design.