change-creation

Generate SPEC.md, PLAN.md, and INDEX.md change packages with dynamic phases.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill change-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-creation
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/change-creation
Command: npx skills add https://github.com/LiorCohen/sdd --skill change-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Change management often requires scaffolding consistent SPEC.md and PLAN.md, which can lead to inconsistent results and slower delivery.

Core Features & Use Cases

  • Generate a complete change package with SPEC.md, PLAN.md, and INDEX.md updates.
  • Dynamically derive implementation phases from project settings and affected components.
  • Support for feature, bugfix, refactor, and epic types.

Quick Start

Describe a new change by providing its name, type, title, and description, then run the skill to generate SPEC.md and PLAN.md.

Frequently Asked Questions about change-creation

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

FAQPage Schema
How do I automate change spec and implementation plan generation for a new feature?

To automate change spec and implementation plan generation, provide the change name, type, title, and description. The skill outputs consistent SPEC.md, PLAN.md, and INDEX.md files by dynamically deriving phases from project settings and affected components.

What is the best way to scaffold SPEC.md and PLAN.md for a bugfix or refactor?

Scaffolding SPEC.md and PLAN.md for a bugfix or refactor is best handled by validating the change type and description inputs. The skill reads project settings to dynamically generate implementation phases and updates the index file automatically.

Does this change management workflow support epic-level changes or just single features?

This change management workflow fully supports epic-level changes alongside features, bugfixes, and refactors. It dynamically derives implementation phases from affected components and applies consistent SPEC.md, PLAN.md, and INDEX.md outputs for any supported change type.

Can I generate project management plans without manually defining implementation phases?

Yes, you can generate project management plans without manually defining phases. The skill reads project settings and affected components to dynamically derive implementation phases, ensuring the PLAN.md output is structured automatically without manual phase input.

Why does generating SPEC.md and PLAN.md manually lead to inconsistent project delivery?

Generating SPEC.md and PLAN.md manually leads to inconsistent project delivery because the process lacks standardized phase derivation and input validation. Automating the change package creation ensures consistent outputs and dynamically aligned implementation phases.

What inputs do I need to provide to generate a complete change package with SPEC.md and PLAN.md?

To generate a complete change package with SPEC.md and PLAN.md, you need to provide the change name, type, title, and description. The skill validates these inputs, reads project settings, and returns the file paths along with the index update status.