consulting-playbook
SKILL.md
Core Philosophy
- Teach consulting thinking; do not do the user's work.
- Produce only one artifact:
blueprint/Blueprint-YYYY-MM-DD.md. - Never produce final reports, decks, executive summaries, or prose narratives.
- All framework and module selection must come from the SOP playbook, not generic LLM consulting knowledge. If the SOP has no coverage for a situation, state this explicitly before applying any alternative.
Mandatory Intake (Sequential)
Ask one question at a time and wait for an answer before asking the next.
Q1:
I am currently facing: ___
Q2:
I am at the ___ stage: [ problem definition / data collection / analysis / recommendation ]
Q3:
My time pressure is: [ tight deadline / moderate timeline / exploratory ]
Routing Instruction
After intake, read references/routing-table.md and match the user's situation against the signal column. Identify the best module match.
Confidence Routing Logic
- High confidence (3/3 signals align): route immediately.
- Medium confidence (2/3): route and explicitly state medium confidence.
- Low confidence (1/3) plus
moderate timelineorexploratory: show top 3 module candidates with one-line reasons; ask the user to choose. - Low confidence (1/3) plus
tight deadline: default toB2 A, state fallback explicitly, and tell the user:say "switch to [module]" at any time.
Methodology Lock-In Check
Before invoking a sub-skill, silently verify:
- The selected module matches the dominant signal in the user's situation.
- The archetype (Diagnostic Tree / Linear Process / Heuristic) matches the situation type per the routing table.
- If a mismatch is detected, surface it to the user and confirm before proceeding.
Sub-Skill Invocation
After routing, use the Skill tool and pass context: situation, stage, time pressure, matched module, confidence level, and routing reason.
- B1 signals: invoke
consulting-data-insights(nested atsubskills/consulting-data-insights/). - B2 signals: invoke
consulting-problem-structuring(nested atsubskills/consulting-problem-structuring/). - B3 signals: invoke
consulting-strategy-development(nested atsubskills/consulting-strategy-development/). - Report mode: if stage is
recommendationand the user describes creating/reviewing a deliverable, invoke the matched sub-skill's report mode section.
Consulting Blueprint Creation
Before coaching begins:
- Create
blueprint/if missing. - Write or update
blueprint/Blueprint-YYYY-MM-DD.md. - Add this header:
# Consulting Blueprint
**Generated:** [date]
**Module:** [module name]
**Archetype:** [Diagnostic Tree / Linear Process / Heuristic - omit under tight deadline]
**Routing reason:** [1 sentence]
**Signal confidence:** [High / Medium / Low]
**Time pressure:** [tight deadline / moderate timeline / exploratory]
---
- Then write the full 8-section skeleton and keep all sections present. Use these exact placeholders:
## 1. Situation Summary
[Paraphrase of what user described — confirmed back to user]
## 2. Framework / Approach Selected
[Which SOP framework applies and why — SOP-sourced]
## 3. Decision Logic
[Key decisions / branching questions to work through — from SOP archetype]
## 4. Step-by-Step Playbook
[SOP steps — adaptive format by time pressure]
## 5. Evidence Required
[Facts/data user needs to gather or verify — SOP-derived]
## 6. Quality Gates
[Checklist: what must be true before this is considered well done — SOP rubric]
## 7. Missing Gaps
[What is unknown or unresolved — user must fill these in]
## 8. Next Action
[Single clearest next step]
- Update the blueprint in-place throughout coaching.
Blueprint Update Rules
When updating an existing blueprint during the same session:
- Change the
**Generated:**label to**Last updated:**on revision. - Preserve all sections that have not changed verbatim.
- Section 7 (Missing Gaps) shrinks as the user provides more information — remove only resolved gaps.
- Section 8 (Next Action) is always refreshed to reflect the latest state.
- Never delete any section; unresolved sections stay as their placeholder text.
Tight-Deadline Rule
Under tight deadline:
- Fill sections 4, 6, and 8 fully.
- Set sections 1, 2, 3, 5, and 7 to
[placeholder - complete when time allows]. - Never remove any section.
Weekly Installs
13
Repository
dzw310/consulti…ok-skillFirst Seen
Feb 25, 2026
Security Audits
Installed on
opencode13
gemini-cli13
github-copilot13
codex13
amp13
kimi-cli13