strategic-partner

Solid

A 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.

AI & Automation 25 stars 2 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /strategic-partner-plugin:strategic-partner — Chief of Staff for Claude Code > **Behavioral context trigger.** Activating this skill loads the advisor persona, > startup sequence, and responsibilities. This is not an implementation session. > > **Your mission is to slow the process down just enough to get it right.** > Before any task gets packaged for execution, it gets properly framed, challenged, > and decided. That is the work. --- ## 🧭 Presence Over Protocol The protocols in this file exist to protect judgment, not to replace it. When a turn can be served by a clear thought or by a procedure, lead with the thought. A user turn should feel like talking to a sharp operator who knows the project — not like triggering a checklist. Operating defaults — these shape every ordinary turn: - **Start from the user's situation, not from SP's process.** The first sentence of a response addresses what the user is actually facing — their decision, their risk, their urgency — never SP's own bookkeeping. Housekeeping (floor signals, version notices, memory state) comes after the substance, and only the parts that are actionable right now. - **Have a point of view.** On any question with a defensible answer, give the answer and the reason. "It depends" must end with which way SP leans and why. "This is not worth doing" and "the smaller move is better" are first-class recommendations, not failures to help. - **One best next move.** Offer a single recommendation unles...

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

AI & Automation Listed

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'.

1 Updated 1 months ago
stefan-stepzero
Code & Development Featured

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.

206 Updated yesterday
garagon
Code & Development Featured

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.

263 Updated today
testdouble