How do I install the Ae Sdd Specs skill?

Run npx skillmds@latest add shanepadgett/ae-sdd-specs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ae Sdd Specs skill do?

Write change-set specifications for change It is listed under Coding & Dev Tools on SkillMD.

Is Ae Sdd Specs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ae Sdd Specs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ae Sdd Specs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ae Sdd Specs?

shanepadgett (@shanepadgett) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ae Sdd Specs by shanepadgett — Agent Skill

Name: Ae Sdd Specs
Rating: 4.666666666666667 (3 reviews)
Author: shanepadgett

File contents

Specs

Write change-set specifications for the change set.

Required Skills

spec-driven-development (state management, phase gates)
spec-format
research

Inputs

[!IMPORTANT] Resolve the change set by running ls changes/ | grep -v archive/. If exactly one directory exists, use it. Only prompt the user when multiple change sets are present.

Instructions

Load spec-driven-development, spec-format, and research skills. Read state from changes/<name>/state.toml and proposal.md. Apply state entry check per skill guidelines.
Lane check: If lane is not full, redirect to appropriate command per skill guidelines.
Spec writing is collaborative. Don't start writing immediately. First, summarize the goal, actors, workflows, and constraints in your own words. Explain how the change maps to the existing capability hierarchy. Present concrete statements and decisions. Offer options for open decisions. Pause and wait for user confirmation.
After confirmation, run ae sdd spec list (no flag by default) to discover canonical spec paths, then use research skill to understand related capabilities, naming conventions, and build context for spec writing. If the canonical specs directory does not exist yet, treat this as greenfield and proceed.
With approval, create specs in changes/<name>/specs/ using spec-format skill:
- Specs may be nested by domain
- Use EARS syntax for requirements
- Review specs for atomic, testable, implementation-agnostic requirements
Suggest ae-sdd-critique specs when complete for review.
Do not update phase status in this command. When the user wants to proceed, suggest ae-sdd-next <name>.

Examples

Writing specs with collaborative discovery:

Input: None (change: "password-reset")
Output: "Your goal is to allow users to reset passwords via email. 
        Actors: user, admin. Workflow: request email → click link → set new password. Correct?"
       User confirms.
       Output: "This maps to auth/password spec boundary. 
                Writing delta spec at changes/password-reset/specs/auth/password.md..."

Lane check redirects:

Input: "vibe-lane" (not full lane)
Output: "Vibe lane should skip specs—redirecting to ae-sdd-plan."

---name: ae-sdd-specsdescription: Write change-set specifications for change---# SpecsWrite change-set specifications for the change set.## Required Skills- `spec-driven-development` (state management, phase gates)- `spec-format`- `research`## Inputs> [!IMPORTANT]> Resolve the change set by running `ls changes/ | grep -v archive/`. If exactly one directory exists, use it. Only prompt the user when multiple change sets are present.## Instructions1. Load `spec-driven-development`, `spec-format`, and `research` skills. Read state from `changes/<name>/state.toml` and `proposal.md`. Apply state entry check per skill guidelines.2. **Lane check**: If lane is not `full`, redirect to appropriate command per skill guidelines.3. Spec writing is collaborative. Don't start writing immediately. First, summarize the goal, actors, workflows, and constraints in your own words. Explain how the change maps to the existing capability hierarchy. Present concrete statements and decisions. Offer options for open decisions. Pause and wait for user confirmation.4. After confirmation, run `ae sdd spec list` (no flag by default) to discover canonical spec paths, then use `research` skill to understand related capabilities, naming conventions, and build context for spec writing. If the canonical specs directory does not exist yet, treat this as greenfield and proceed.5. With approval, create specs in `changes/<name>/specs/` using `spec-format` skill: - Specs may be nested by domain - Use EARS syntax for requirements - Review specs for atomic, testable, implementation-agnostic requirements6. Suggest `ae-sdd-critique specs` when complete for review.7. Do not update phase status in this command. When the user wants to proceed, suggest `ae-sdd-next <name>`.## Examples**Writing specs with collaborative discovery:**```textInput: None (change: "password-reset")Output: "Your goal is to allow users to reset passwords via email. Actors: user, admin. Workflow: request email → click link → set new password. Correct?" User confirms. Output: "This maps to auth/password spec boundary. Writing delta spec at changes/password-reset/specs/auth/password.md..."```**Lane check redirects:**```textInput: "vibe-lane" (not full lane)Output: "Vibe lane should skip specs—redirecting to ae-sdd-plan."```

Frequently asked questions

Ae Sdd Specs