Skip to content

LiorCohen/sdd / plugin/core/skills/change-creation

change-creation

Verified

Create change specification and implementation plan with dynamic phase generation. Supports feature, bugfix, refactor, and epic types.

FileKindSize
SKILL.mdskill md10.6 KB
schemas/input.schema.jsonconfig3.4 KB
schemas/output.schema.jsonconfig1.0 KB
templates/spec-bugfix.mdmarkdown868 B
templates/spec-epic.mdmarkdown965 B
templates/spec-feature.mdmarkdown9.5 KB
templates/spec-refactor.mdmarkdown3.9 KB

schemas/input.schema.json

View on GitHub
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Change Creation Input",
  "description": "Input parameters for creating a new change (feature, bugfix, refactor, or epic) in the SDD workflow.",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Directory name for the change (lowercase, hyphens, no spaces)"
    },
    "type": {
      "type": "string",
      "enum": [
        "feature",
        "bugfix",
        "refactor",
        "epic"
      ],
      "description": "Type of change being created"
    },
    "title": {
      "type": "string",
      "description": "Display title for the change"
    },
    "description": {
      "type": "string",
      "description": "Brief description of the change (1-2 sentences)"
    },
    "domain": {
      "type": "string",
      "description": "Primary business domain for the change"
    },
    "issue": {
      "type": "string",
      "description": "Issue reference (e.g., PROJ-123)"
    },
    "mode": {
      "type": "string",
      "enum": [
        "spec-only",
        "full"
      ],
      "default": "full",
      "description": "Processing mode: spec-only creates only SPEC.md, full creates both SPEC.md and PLAN.md"
    },
    "workflow_id": {
      "type": "string",
      "description": "Workflow ID for change-id assignment (directory format: <id>-<name>)"
    },
    "change_id": {
      "type": "string",
      "description": "Pre-assigned change ID from workflow-state (format: <name>-<seq>, e.g. user-auth-1)"
    },
    "source_content": {
      "type": "string",
      "description": "Full markdown content to embed in Original Requirements section"
    },
    "decomposition_id": {
      "type": "string",
      "description": "UUID linking related changes from a decomposition"
    },
    "prerequisites": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Prerequisite change names that must be completed first"
    },
    "affected_components": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Component names from sdd-settings.yaml affected by this change"
    },
    "child_changes": {
      "type": "array",
      "description": "Child change definitions for epic type changes",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Child change directory name"
          },
          "title": {
            "type": "string",
            "description": "Child change display title"
          },
          "description": {
            "type": "string",
            "description": "Brief description of the child change"
          },
          "dependencies": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Names of other child changes this one depends on"
          }
        }
      }
    },
    "acceptance_criteria": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Epic-level acceptance criteria (for epic type changes)"
    },
    "cross_cutting_concerns": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Cross-cutting concerns spanning multiple child changes (for epic type changes)"
    }
  },
  "required": [
    "name",
    "type",
    "title",
    "description",
    "domain"
  ]
}
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall