Awesome-omni-skill ae-sdd-init

Name: ae-sdd-init
Author: diegosouzapw

Initialize a new SDD change set after user-approved naming

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/ae-sdd-init" ~/.claude/skills/diegosouzapw-awesome-omni-skill-ae-sdd-init && rm -rf "$T"

manifest: skills/development/ae-sdd-init/SKILL.md

source content

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-development
```
first.
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-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"