Initialize SDD Change Set

VerifiedSafe

Initializes a new SDD change set via the CLI after collaboratively deriving a kebab-case name and getting explicit user approval. Helps start a structured change proposal with the SDD tool, avoiding manual scaffolding.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#sdd#change-set#initialization#approval#cli

Recommended for

Automated summary

Initializes a new SDD change set after collaboratively deriving a name and getting explicit user approval.

Strengths

  • Ensures human validation before any change set creation
  • Automates creation via SDD CLI without manual scaffolding
  • Guides user with actionable and specific naming
  • Suggests a follow-up command after initialization

Limitations

  • Requires the spec-driven-development skill to be loaded first
  • Depends on the ae sdd init CLI being installed
  • May slow down the process if the user rejects multiple names
When to use it

Use this skill when you need to create a new SDD change set and want to ensure the name is approved before initialization.

When not to use it

Do not use it if you need to quickly initialize a change set without human interaction or if the name is already predetermined and doesn't need approval.

Security analysis

Safe
Quality score85/100

The skill runs a specific CLI command 'ae sdd init' with a user-approved kebab-case name, which poses no meaningful risk of code injection or destructive actions.

No concerns found

How this analysis is made

Examples

Initialize webhook retry change set
I want to propose retry behavior for failed webhooks

name: ae-sdd-init description: Initialize a new SDD change set after user-approved naming

SDD Init

Create a new change set with the SDD CLI after collaboratively deriving a strong name and getting explicit user approval.

Required Skills

  • spec-driven-development (load first; use CLI-driven initialization workflow)

Inputs

  • Intent Context: What the user wants to propose or change.
  • Proposed Change Set Name: Derived from user intent and naming conventions.

Instructions

  1. Load SDD Context: Load spec-driven-development first.

  2. Derive Candidate Name:

    • Ask the user what they want to propose (or use the current request context if already provided).
    • Propose a concise kebab-case name that reflects the intended change.
    • Keep names action-oriented and specific (for example: add-passwordless-login, improve-checkout-retries).
  3. Require Explicit Approval:

    • Ask the user to approve the proposed change set name.
    • If the user declines, iterate with a revised name.
    • Do not initialize anything until the user explicitly approves a final name.
  4. Initialize via CLI:

    • After approval, run:
    ae sdd init <approved-name>
    
    • Use the SDD CLI only. Do not hand-roll changes/<name>/ scaffolding.
  5. Confirm Result:

    • Report the approved name and that initialization completed.
    • Suggest the next command based on status output (typically ae sdd status <approved-name>).

Success Criteria

  • spec-driven-development skill is loaded before init flow.
  • A change set name is collaboratively derived from user intent.
  • The user explicitly approves the final name.
  • Initialization is performed using ae sdd init <approved-name>.
  • The user receives a clear next command.

Usage Example

User intent: "I want to propose retry behavior for failed webhooks"
Agent: "Proposed change set name: improve-webhook-retry-behavior. Does that name work for you?"
User: "Yes"
Agent runs: ae sdd init improve-webhook-retry-behavior
Agent: "Initialized improve-webhook-retry-behavior. Next: ae sdd status improve-webhook-retry-behavior"

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/initialize-sdd-change-set-mm5t8cf9' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/initialize-sdd-change-set-mm5t8cf9/download' --output '.skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md.part' && mv '.skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md.part' '.skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md' && test -s '.skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ae-sdd-init' && cp -R '.skill-downloads/initialize-sdd-change-set-mm5t8cf9' '.claude/skills/ae-sdd-init'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/initialize-sdd-change-set-mm5t8cf9'

openskills read 'initialize-sdd-change-set-mm5t8cf9'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/initialize-sdd-change-set-mm5t8cf9/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills