shape-spec

name	shape-spec
description	Create a timestamped feature-spec folder with structured plan, decisions, and references for multi-session features. Use to capture a spec before building something non-trivial. To validate the idea first use /office-hours; to execute it use /feature-cycle.
user-invocable	true

Shape Spec

Core Rule

Force structured planning into a timestamped folder before multi-session work. Never start coding from this skill — it precedes implementation.

When to Use

Invoke with /shape-spec when:

• Planning a feature that will span multiple sessions
• Decisions and context should be preserved beyond the current session
• The feature requires significant research or tradeoff analysis
• You want structured handoff context for another session or developer

Process

Phase 1: Name and Scope

1. Ask: "What feature are we speccing?" — get a short name
2. Create the spec folder: tasks/specs/<date>-<name>/
3. Confirm scope boundaries — what's in, what's out

Phase 2: Shape the Plan

Gather structured information through conversation:

1. Goal — What does "done" look like?
2. Context — Why is this needed now? What triggered it?
3. Approach — What's the implementation strategy?
4. Files to touch — Which files need changes?
5. Open questions — What needs clarification?
6. Risks — What could go wrong?