shipkit-engineering-definitionlisted

# shipkit-engineering-definition — Technical Approach Defines HOW we build the product defined in product-definition.json. For each feature, designs the technical mechanisms, captures design decisions, recommends stack direction (greenfield), and defines component structure. This is the engineering blueprint — it takes the product's features and UX patterns and defines the technical approach to implement them. Downstream skills (goals, spec) read both product-definition.json and engineering-definition.json. Architecture decisions are captured directly in this file. --- ## When to Invoke **User triggers**: - "How should we build this?", "Technical approach", "Engineering design" - "Define mechanisms", "Component structure", "Technical decisions" - "Stack direction", "What technologies?" **Workflow position**: - After `/shipkit-product-definition` (needs features and UX patterns) - Before `/shipkit-product-goals` and `/shipkit-engineering-goals` (goals derive criteria from mechanisms) --- ## Prerequisites **Required** (fail gracefully if missing): - `.shipkit/product-definition.json` — features, UX patterns, differentiators **Recommended** (enrich the proposal): - `.shipkit/why.json` — project purpose and vision - `.shipkit/goals/strategic.json` — project stage and constraints - `.shipkit/stack.json` — existing technology constraints - `.shipkit/product-discovery.json` — pain points for traceability **Optional** (for existing projects): - `.shipkit/codebase-index.jso