How do I install the Ae Sdd Bug skill?

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

Fast-track bug investigation and fix initialization It is listed under Coding & Dev Tools on SkillMD.

Is Ae Sdd Bug 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 Bug?

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

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

Who published Ae Sdd Bug?

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

Ae Sdd Bug by shanepadgett — Agent Skill

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

File contents

SDD Bug

Required Skills

spec-driven-development (load first; resolve/init change sets and drive lane/phase/task commands)
research

Inputs

[!IMPORTANT] Resolve required inputs from the workspace first; only ask the user when resolution is ambiguous or missing (for example, multiple change sets exist).

Bug Context: Ask for error messages, reproduction steps, or a description of what is failing.
Change Set Name: Resolve by checking existing change sets. If only one exists, proceed with it; if multiple exist, ask whether this is new or related to an existing one. If none exist, ask the user to confirm or provide a name for the new change set (e.g., fix-login-error).

Instructions

Load SDD Context: Load spec-driven-development, resolve the active change set, and run ae sdd status [name].
Triage: Determine if this is an Actual Bug (code fails to meet existing specs/intent) or a Behavioral Change (new capability requested). If it is a change request, redirect to full lane.
Create Change Set When Needed: If no change set exists, initialize via CLI:
```
ae sdd init <name> --lane bug
```
Do not hand-roll scaffolding or use deprecated custom init commands.
Research: Use the research skill to locate the problem, trace the execution path, and identify the root cause. Compare findings against existing specs.
Document: Create changes/<name>/context.md with:
- Problem description
- Expected behavior
- Root cause (from research)
- High-level fix approach
Next Steps: Do not auto-advance phase from this command. After triage artifacts are complete, suggest ae-sdd-next <name>.

Success Criteria

Bug triaged correctly (actual bug vs behavioral change)
Change set initialized with correct bug lane configuration
Root cause documented in context.md
Phase ready for planning

Usage Examples

Do: Triage before fixing

"This appears to be a regression where the login button is disabled on mobile. I'll initialize a bug lane change set fix-mobile-login to research the root cause."

Don't: Assume CLI arguments

Avoid starting work before resolving bug context and active change set.

---name: ae-sdd-bugdescription: Fast-track bug investigation and fix initialization---# SDD Bug## Required Skills- `spec-driven-development` (load first; resolve/init change sets and drive lane/phase/task commands)- `research`## Inputs> [!IMPORTANT]> Resolve required inputs from the workspace first; only ask the user when resolution is ambiguous or missing (for example, multiple change sets exist).- **Bug Context**: Ask for error messages, reproduction steps, or a description of what is failing.- **Change Set Name**: Resolve by checking existing change sets. If only one exists, proceed with it; if multiple exist, ask whether this is new or related to an existing one. If none exist, ask the user to confirm or provide a name for the new change set (e.g., `fix-login-error`).## Instructions1. **Load SDD Context**: Load `spec-driven-development`, resolve the active change set, and run `ae sdd status [name]`.2. **Triage**: Determine if this is an **Actual Bug** (code fails to meet existing specs/intent) or a **Behavioral Change** (new capability requested). If it is a change request, redirect to full lane.3. **Create Change Set When Needed**: If no change set exists, initialize via CLI: ```bash ae sdd init <name> --lane bug ``` Do not hand-roll scaffolding or use deprecated custom init commands.4. **Research**: Use the `research` skill to locate the problem, trace the execution path, and identify the root cause. Compare findings against existing specs.5. **Document**: Create `changes/<name>/context.md` with: - Problem description - Expected behavior - Root cause (from research) - High-level fix approach6. **Next Steps**: Do not auto-advance phase from this command. After triage artifacts are complete, suggest `ae-sdd-next <name>`.## Success Criteria- Bug triaged correctly (actual bug vs behavioral change)- Change set initialized with correct `bug` lane configuration- Root cause documented in `context.md`- Phase ready for planning## Usage Examples### Do: Triage before fixing"This appears to be a regression where the login button is disabled on mobile. I'll initialize a bug lane change set `fix-mobile-login` to research the root cause."### Don't: Assume CLI argumentsAvoid starting work before resolving bug context and active change set.

Frequently asked questions

Ae Sdd Bug