How do I install the Ae Sdd Next skill?

Run npx skillmds@latest add shanepadgett/ae-sdd-next 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 Next skill do?

Advance to the next SDD phase with artifact checks It is listed under Coding & Dev Tools on SkillMD.

Is Ae Sdd Next safe to use?

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

Which AI agents work with Ae Sdd Next?

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 Next free to use?

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

Who published Ae Sdd Next?

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

Ae Sdd Next by shanepadgett — Agent Skill

Name: Ae Sdd Next
Rating: 4.5 (4 reviews)
Author: shanepadgett

File contents

SDD Next

Advance the active change set to the next phase only after verifying current-phase artifacts exist.

ae-sdd-next is the single versatile phase-transition command. For full-lane work, use it for both directions between plan and implement by delegating transition decisions to CLI guards.

Required Skills

spec-driven-development (state management, phase sequencing, guardrails)

Inputs

[!IMPORTANT] Resolve the active change set from workspace state first. Ask the user only when multiple change sets are present.

Instructions

Load spec-driven-development and run ae sdd status [name].
Identify lane and current phase.
Verify required artifacts for the current phase before advancing:
- full/proposal: changes/<name>/proposal.md exists.
- full/specs: changes/<name>/specs/ exists and contains at least one .md spec.
- full/discovery: changes/<name>/thoughts/ exists and contains at least one discovery note.
- full/tasks: changes/<name>/tasks.toml exists and contains at least one task entry.
- full/plan: changes/<name>/plans/ exists and contains the current task plan.
- full/implement: changes/<name>/tasks.toml exists and task state is valid (no more than one in_progress task).
- full/reconcile: changes/<name>/reconciliation.md exists.
- vibe/context and bug/triage: changes/<name>/context.md exists.
- vibe/plan and bug/plan: changes/<name>/plan.md exists.
- vibe/reconcile and bug/reconcile: changes/<name>/reconciliation.md exists.
If artifacts are missing, do not advance. Report exactly what is missing and suggest the command to produce/fix it.
Full-lane transition behavior between plan and implement must be deterministic and delegated to CLI guards:
- From plan, running ae sdd phase complete --next [name] advances to implement.
- From implement, running ae sdd phase complete --next [name] is versatile:
  - tasks remaining: loop back to plan
  - tasks complete: advance to reconcile
- Always use this single CLI transition path; do not manually branch phases in workflow command logic.
If artifacts are present, advance phase by running:
```
ae sdd phase complete --next [name]
```
Report the transition result and the new phase from status output.

Success Criteria

Phase progression happens only after artifact checks pass.
Missing artifacts block progression with actionable guidance.
Successful progression is explicit and visible in status output.

---name: ae-sdd-nextdescription: Advance to the next SDD phase with artifact checks---# SDD NextAdvance the active change set to the next phase only after verifying current-phase artifacts exist.`ae-sdd-next` is the single versatile phase-transition command. For full-lane work, use it for both directions between `plan` and `implement` by delegating transition decisions to CLI guards.## Required Skills- `spec-driven-development` (state management, phase sequencing, guardrails)## Inputs> [!IMPORTANT]> Resolve the active change set from workspace state first. Ask the user only when multiple change sets are present.## Instructions1. Load `spec-driven-development` and run `ae sdd status [name]`.2. Identify lane and current phase.3. Verify required artifacts for the current phase before advancing: - **full/proposal**: `changes/<name>/proposal.md` exists. - **full/specs**: `changes/<name>/specs/` exists and contains at least one `.md` spec. - **full/discovery**: `changes/<name>/thoughts/` exists and contains at least one discovery note. - **full/tasks**: `changes/<name>/tasks.toml` exists and contains at least one task entry. - **full/plan**: `changes/<name>/plans/` exists and contains the current task plan. - **full/implement**: `changes/<name>/tasks.toml` exists and task state is valid (no more than one `in_progress` task). - **full/reconcile**: `changes/<name>/reconciliation.md` exists. - **vibe/context** and **bug/triage**: `changes/<name>/context.md` exists. - **vibe/plan** and **bug/plan**: `changes/<name>/plan.md` exists. - **vibe/reconcile** and **bug/reconcile**: `changes/<name>/reconciliation.md` exists.4. If artifacts are missing, do not advance. Report exactly what is missing and suggest the command to produce/fix it.5. Full-lane transition behavior between `plan` and `implement` must be deterministic and delegated to CLI guards: - From `plan`, running `ae sdd phase complete --next [name]` advances to `implement`. - From `implement`, running `ae sdd phase complete --next [name]` is versatile: - tasks remaining: loop back to `plan` - tasks complete: advance to `reconcile` - Always use this single CLI transition path; do not manually branch phases in workflow command logic.6. If artifacts are present, advance phase by running: ```bash ae sdd phase complete --next [name] ```7. Report the transition result and the new phase from status output.## Success Criteria- Phase progression happens only after artifact checks pass.- Missing artifacts block progression with actionable guidance.- Successful progression is explicit and visible in status output.

Frequently asked questions

Ae Sdd Next