ae-sdd-init
Initialize a new SDD change set after user-approved naming
Best use case
ae-sdd-init is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Initialize a new SDD change set after user-approved naming
Teams using ae-sdd-init should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ae-sdd-init/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ae-sdd-init Compares
| Feature / Agent | ae-sdd-init | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Initialize a new SDD change set after user-approved naming
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: ```bash 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 ```text 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" ```
Related Skills
affinity-python-sdk
Use when writing Python code with the Affinity SDK, or when user asks about "affinity-sdk", "affinity package", typed IDs, async Affinity client, pagination, or Python scripts for Affinity CRM.
trinity-auto-boot-validator
Generated skill from request: trinity auto-boot validator
speckit-initial
Run `specify init` in the current or target directory to bootstrap a Spec Kit project (pull .specify/ and slash commands); supports multiple AI agents and --script sh/ps. Use when the user says "initialize Spec Kit project", "specify init", or "set up Spec Kit in this repo".
minitest-testing
Write, review, and improve Minitest tests for Ruby on Rails applications. Covers model tests, controller tests, system tests, fixtures, and best practices from Rails Testing Guide.
init
Initialize warehouse schema discovery. Generates .astro/warehouse.md with all table metadata for instant lookups. Run once per project, refresh when schema changes. Use when user says "/data:init" or asks to set up data discovery.
aix-init
Initialize or upgrade aix framework in a project. Detects tech stack, generates appropriate tier structure, and sets up Claude Code integration.
session-init
Initializes session with environment check and task status overview. Use when user mentions セッション開始, 作業開始, 状況確認, what should I work on, start session. Do NOT load for: 実装作業, レビュー, セッション途中の作業.
always-init
Universal task initializer that automatically loads PAI context for all user requests. Ensures complete context availability (contacts, preferences, protocols) before responding to any task. (project, gitignored)
agentuity-cli-project-auth-init
Set up Agentuity Auth for your project. Requires authentication. Use for managing authentication credentials
affinity-mcp-workflows
Use when working with Affinity CRM via MCP tools - find entities, manage workflows, log interactions, prepare briefings, find warm intros. Also use when user mentions "pipeline", "deals", "relationship strength", or wants to prepare for meetings.
init-agents
Initialize or update AGENTS.md (or CLAUDE.md for Claude Code) with AI agent guidance. Use when user says 'init agents', 'create AGENTS.md', 'setup agent instructions', or wants project-specific AI coding assistant configuration.
agent-sdk-definitions
Programmatic agent definitions for the Claude Agent SDK in TypeScript and Python. Use when creating agents for SDK-based applications rather than filesystem-based Claude Code.