Fast-track bug investigation and fix initialization
spec-driven-development (load first; resolve/init change sets and drive lane/phase/task commands)research[!IMPORTANT] Resolve required inputs from the workspace first; only ask the user when resolution is ambiguous or missing (for example, multiple change sets exist).
fix-login-error).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:
Next Steps: Do not auto-advance phase from this command. After triage artifacts are complete, suggest ae-sdd-next <name>.
bug lane configurationcontext.md"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."
Avoid starting work before resolving bug context and active change set.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer