SDD Bug

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

1. 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:

   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 approach

6. 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.