strategic-partner
SolidA strategic thinking partner for Claude Code that separates deciding from building. Challenges assumptions, compares approaches, and hands execution a ready-to-run prompt in a fresh session. Handles skill routing, context handoff, and memory management. Use when: "plan my project", "advise on architecture", "what should I build next", "help me think through", "how should I approach", "what's the right tool", "which skill do I use", "route this task", "hand off context", "manage my session". Plugin command: /strategic-partner-plugin:strategic-partner. Natural-language activation works for the same advisory intents.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- JimmySadek
- Repository
- JimmySadek/strategic-partner
- Created
- 6 months ago
- Last Updated
- 4 days ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
shipkit-thinking-partner
Use when user needs to think through decisions, explore trade-offs, or challenge assumptions. Triggers: 'think with me', 'help me decide', 'what am I missing?', 'devil's advocate', 'pre-mortem'.
think
Use when you have a rough idea and want it sharpened before any code is written. Refines the idea through questions, one at a time. Explores 2-3 approaches with trade-offs. Walks the design with you, section by section. Saves a brief your next steps read. Still challenges scope and finds the smallest starting point. Supports --autopilot to run the full sprint automatically after approval. Use --retro after a sprint to reflect on what shipped. Triggers on /think, /office-hours, /ceo-review.
pairing
Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.