shipkit-thinking-partner

# shipkit-thinking-partner - Cognitive Thinking Partner **Purpose**: Facilitate structured thinking through decisions, trade-offs, and unknowns using cognitive frameworks. Forces genuine dialogue by restricting tool access — Claude becomes a thinking partner, not a doer. **Key innovation**: The tool restriction IS the feature. No Write, Edit, or Bash access means Claude cannot jump to implementation. Discussion summary stays in conversation; persistence is delegated to other skills. --- ## When to Invoke **User triggers**: - "Help me think through..." - "Think with me about..." - "Let's discuss..." - "What am I missing?" - "Devil's advocate this" - "Pre-mortem this decision" - "I'm torn between..." - "What are the trade-offs?" - "Challenge my thinking" **Adversarial-mode triggers** (route to the autonomous debate, not the interactive flow): - "Debate this" - "Stress test this decision" - "Adversarial analysis" - "Argue for and against" - "Resource tradeoff" - "What would [time / cost / scope / UX / risk] say about this?" **Workflow position**: - Before `/shipkit-spec` (clarify what to build) - Before `/shipkit-engineering-definition` (think through decisions before capturing) - Before `/shipkit-plan` (explore approaches before committing) - Standalone for any decision that needs structured thinking --- ## Prerequisites **Recommended**: - `.shipkit/why.json` — Project vision provides decision-making context - `.shipkit/architecture.json` — Existing decisions constrai...