Agent workflow: replace superpowers with cc-sdd

Status: Open — Phase 1, confirmation needed

Problem

The current spec workflow uses obra/superpowers and stores committed design/spec docs in docs/superpowers/specs/. Those specs are version-controlled, but they are not part of the Starlight site and the command surface is tied to one plugin/tooling stack.

Goal

Establish a repo-committed, docs-first spec workflow. If cc-sdd (gotalab/cc-sdd) is adopted, treat .claude/commands/ as one client wrapper; the canonical artifact should still be the spec page under docs/src/content/docs/internal/specs/, browsable at jackin.tailrocks.com/internal/specs/.

What superpowers provides today

Brainstorming skill → spec authoring
Writing-plans skill → implementation plan
TDD, debugging, review skills
Specs at docs/superpowers/specs/

cc-sdd equivalent

/spec command → creates or updates a spec MDX page at docs/src/content/docs/internal/specs/
/plan command → creates an implementation plan
/execute command → implements against the spec
.claude/commands/*.md stays a Claude-facing wrapper, not the canonical cross-agent source of truth

Steps

Create the canonical spec location and template under docs/src/content/docs/internal/specs/ (depends on Developer Reference setup).
Decide whether cc-sdd is the wrapper to adopt; if yes, install it and point .claude/commands/spec.md, plan.md, and execute.md at the canonical spec location.
Add a short repo-level note to AGENTS.md explaining the chosen wrapper and where specs live.
Migrate high-value existing specs from docs/superpowers/specs/ into the Starlight-backed internal-specs area.
Remove the superpowers plugin only after the replacement workflow covers the same day-to-day needs.

What needs confirmation

Whether cc-sdd is the chosen wrapper or just one candidate implementation.
Migration plan for docs/superpowers/specs/ — which specs are for shipped features (convert) vs in-progress (draft pages)?
Whether to remove superpowers immediately or run both in parallel for one PR cycle.