shape

# Shape

Bridge between intent clarification and implementation. Transforms WHAT into HOW.

## When This Skill Activates

- After `/hope:intent` when spec_score >= 5
- Explicit request: "shape this", "how should I build this"
- Implementation approach questions
- Architecture decisions needed before coding

**If spec_score < 5:** Return to `/hope:intent` for clarification first.

---

## Protocol

### 1. Aspect Discovery

Not all aspects apply to every task. Discover which are relevant:

| Aspect | Signal Keywords | When Relevant |
|--------|-----------------|---------------|
| Data | database, schema, storage, persist | Stateful changes |
| API | endpoint, route, request, response | Service boundaries |
| UI | component, display, user, interaction | Visual interfaces |
| Auth | permission, role, access, security | Protected resources |
| Performance | fast, scale, concurrent, cache | High-traffic paths |
| Error | fail, recover, retry, fallback | Resilience needed |
| Testing | verify, confidence, coverage | Quality requirements |
| Migration | existing, legacy, transition | Brownfield work |
| Integration | third-party, external, sync | Cross-system |
| Deployment | release, rollback, feature flag | Delivery concerns |

**Rule:** Only shape aspects that appear in the spec or have clear dependencies.

---

### 2. Expert Consultation

For each relevant aspect, consult the appropriate expert:

| Aspect | Anchor Expert | Philosophy |
|--------|---------------|------------|
| Data | Rich Hickey | Immutability, simplicity, facts over place |
| API | Martin Fowler | Pragmatic patterns, evolvability |
| UI | Don Norman | User-centered, affordances, feedback |
| Auth | OWASP | Defense in depth, least privilege |
| Performance | Brendan Gregg | Measure first, optimize bottlenecks |
| Error | Michael Nygard | Stability patterns, circuit breakers |
| Testing | Kent Beck | Test behavior, not implementation |
| Migration | Sam Newman | Strangler fig, incremental migration |
| I