skills.rest
Visma-Tech-LT
Visma-Tech-LTOFFICIAL
Explore all skills by this author →
GitHub

create-plan

Create a phased implementation plan with measurable success criteria from research and codebase investigation.

3|Updated Apr 10, 2026
Search Tags:#implementation planning#codebase analysis#success criteria#technical documentation#phased plan#spec-driven workflow#interactive scoping
One-click install
npx skills add https://github.com/Visma-Tech-LT/ai-workshop-marketplace --skill create-plan-visma-tech-lt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/Visma-Tech-LT/ai-workshop-marketplace/tree/main/plugins/sdw/skills/create-plan
Command: npx skills add https://github.com/Visma-Tech-LT/ai-workshop-marketplace --skill create-plan-visma-tech-lt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

create-plan converts early research into a detailed, phased implementation plan so you can build the right thing in the right order instead of guessing during development.

Core Features & Use Cases

  • Interactive planning with human-aligned scope: gathers missing context, proposes phases, and iterates until the user approves the structure.
  • Codebase-driven discovery before writing: reads provided files fully, then uses codebase research to ground assumptions and include file/line references.
  • Actionable delivery with verification criteria: produces a plan document that includes success criteria for both automated tests and manual checks, and explicitly defines what is out of scope.

Quick Start

Use create-plan after completing research by providing a relevant research file path or ticket reference, then review the generated plan document and confirm the phases before implementation.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I turn codebase research into an actionable implementation plan?▼

Spec-driven planning generates a time-stamped document in the .claude/ai directory that defines phased implementation steps, measurable automated test criteria, manual verification checks, and explicit out-of-scope boundaries to guide development.

How do I create a phased implementation plan for a new software feature?▼

Codebase-driven discovery reads provided files fully and performs parallel codebase research to ground planning assumptions, ensuring the generated plan includes accurate file and line references for technical documentation rather than relying on guesses.

Do I need prior research outputs before generating a technical build plan?▼

The generated plan document explicitly defines what is out of scope and includes measurable success criteria for both automated tests and manual checks, ensuring verification boundaries are clear before implementation code is written.

What's the best way to structure success criteria in a technical documentation plan?▼

The best way to structure success criteria is to define measurable outcomes for both automated tests and manual checks within a time-stamped plan document, while explicitly stating what features are out of scope to prevent scope creep.

Related Skills

Explore More Software Engineering Skills→
mlopscommunitymlopscommunity
37

objective-research

Separate agent contexts to research code paths and data flow objectively.

Official
Intermediate
atomicinnovationatomicinnovation
30

implement-plan

Execute approved implementation plans and update progress checkboxes.

Official
Advanced
deandumdeandum
3

discovery

Grep the repository to identify related code and write a discovery.md handoff plan.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-refine-issue

Refine software issue documentation via codebase research and gap analysis.

Community
Intermediate