Our review
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
Use this skill when you need to create a new SDD change set and want to ensure the name is approved before initialization.
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
SafeThe 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
Examples
I want to propose retry behavior for failed webhooksname: 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
-
Load SDD Context: Load
spec-driven-developmentfirst. -
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).
-
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.
-
Initialize via CLI:
- After approval, run:
ae sdd init <approved-name>- Use the SDD CLI only. Do not hand-roll
changes/<name>/scaffolding.
-
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-developmentskill 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"
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.