shipkit-spec

# shipkit-spec - Lightweight Feature Specification **Purpose**: Transform feature descriptions into structured JSON specifications with Given/When/Then scenarios and comprehensive edge case coverage, creating clear acceptance criteria for implementation. A **no-gaps completeness gate** (Step 5) ensures the spec names every application, datastore, contract, and integration it implies — so "done" can't mean green-but-not-functional. **Output format**: JSON -- structured data readable by Claude, machine-readable by other tools, and queryable by other skills. --- ## When to Invoke **User triggers**: - "Spec this feature" - "Create a specification" - "What are the requirements?" - "Define the feature properly" - User describes a new feature idea **Before**: - `/shipkit-plan` (this creates the spec that planning needs) - `implement (no skill needed)` (need spec before implementing) **Workflow position**: - After feature concept is clear - Before implementation planning - Can be used standalone for requirement clarification --- ## Prerequisites **Recommended**: - Stack defined: `.shipkit/stack.json` (to understand tech constraints) - Schema defined: `.shipkit/schema.json` (to understand data model) **Optional but helpful**: - Architecture decisions: `.shipkit/architecture.json` - Existing specs: `.shipkit/specs/todo/*.json`, `.shipkit/specs/active/*.json` (check for similar patterns) **If missing**: Infer tech stack from codebase signals (package.json, imports, config fi...