Design and draft strategy deliverables matched to client context. Turns JTBD data into decision matrices, priority maps, delegation frameworks, expectation-setting scripts. Use for "build the deliverable", "what should I give them", "architect this".
From uxinatornpx claudepluginhub jabberlockie/the-human-stack-plugins-public --plugin uxinatorThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Designs and drafts the strategy deliverables Tim's clients actually need. Takes JTBD data, diagnostic results, or session context and produces structured outputs that close the expectation gap. This is Tim's external high-S, high-C function — it does the structured work his profile skips.
Tim generates brilliant strategic insight verbally. Then the call ends and nothing is written down. The client leaves with feelings, not artifacts. Strategy-architect turns insight into deliverables.
Before designing anything, collect context. Use whatever's available — don't block on missing data.
STRATEGY CONTEXT
────────────────
Client: [Organization name]
JTBD Analysis: [Link or paste — if available, this is the primary input]
Diagnostic Scores: [Digital Health scores if available]
Engagement Stage: [Discovery | Diagnostic | Post-Diagnostic | Managed Success | Advisory]
Decision Makers: [Who decides? Who influences? Who implements?]
What They Asked For: [Their words, not Tim's interpretation]
What They Actually Need: [Tim's diagnosis — often different from what they asked]
Previous Deliverables: [What have they already received from Tim?]
Next Touchpoint: [When is the next meeting? What should it accomplish?]
Based on context, select the right deliverable type:
| Client Signal | Deliverable Type |
|---|---|
| "What should we do first?" | Priority Map |
| "Who owns what?" / "Can I delegate?" | Delegation Matrix |
| "How long will this take?" | 90-Day Milestone Map |
| "We need a plan" | Strategic Action Plan |
| "What should we expect?" | Expectation-Setting Script |
| "We're overwhelmed by the data" | Diagnostic Translation Brief |
| "How do we get buy-in?" | Stakeholder Alignment Plan |
| "What's wrong?" / "Why isn't this working?" | Root Cause Analysis |
| Multiple of the above | Engagement Roadmap (combines several) |
For clients who need to know what matters most.
PRIORITY MAP: [Client Name]
Date: [Date] | Prepared by: Tim Lockie, The Human Stack
BASED ON: [Diagnostic scores / JTBD analysis / discovery session]
PRIORITY 1 (Now — next 30 days)
────────────────────────────────
WHAT: [Specific action, not a category]
WHY: [One sentence connecting to their JTBD]
WHO: [Owner name + role]
DONE = [Observable outcome — not "improved" but "X happens"]
RISK IF SKIPPED: [What gets worse]
PRIORITY 2 (Next — 30-60 days)
────────────────────────────────
[Same structure]
PRIORITY 3 (Then — 60-90 days)
────────────────────────────────
[Same structure]
EXPLICITLY NOT NOW:
- [Thing they might expect but shouldn't prioritize yet — and why]
- [Thing they might expect but shouldn't prioritize yet — and why]
NOTE: These priorities assume [stated assumption]. If [condition changes], reprioritize.
For CEOs/leaders asking "what's mine vs. what can I delegate?"
DELEGATION MATRIX: [Client Name]
Date: [Date] | Prepared by: Tim Lockie, The Human Stack
CONTEXT: [Why this matrix exists — usually a CEO bandwidth question]
┌──────────────────────────┬────────────┬────────────┬────────────┐
│ DECISION/ACTION │ [CEO Name] │ [Ops Lead] │ SHARED │
├──────────────────────────┼────────────┼────────────┼────────────┤
│ [Decision 1] │ ● │ │ │
│ [Decision 2] │ │ ● │ │
│ [Decision 3] │ │ │ ● │
│ [Decision 4] │ │ ● │ │
├──────────────────────────┼────────────┼────────────┼────────────┤
│ ESCALATION TRIGGER │ [When ops lead should pull CEO back in] │
│ CHECK-IN CADENCE │ [How often CEO gets updated without owning]│
└──────────────────────────┴───────────────────────────────────────────┘
CEO TIME COMMITMENT: ~[X]% for [Y weeks], decreasing to [Z]% ongoing
For clients who need to see the arc.
90-DAY MILESTONE MAP: [Client Name]
Date: [Date] | Prepared by: Tim Lockie, The Human Stack
DAY 1 DAY 30 DAY 60 DAY 90
│ │ │ │
┌──────┴──────┐ ┌──────┴──────┐ ┌──────┴──────┐ ┌──────┴──────┐
│ FOUNDATION │ │ TRACTION │ │ MOMENTUM │ │ CHECKPOINT │
│ │ │ │ │ │ │ │
│ [Action 1] │ │ [Action 3] │ │ [Action 5] │ │ [Review] │
│ [Action 2] │ │ [Action 4] │ │ [Action 6] │ │ [Decision] │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
EXPECT: EXPECT: EXPECT: EXPECT:
[What it will [What progress [What progress [What "done"
feel like — looks like — looks like — looks like at
probably first signs] real change] this stage]
uncomfortable]
WHAT THIS PLAN DOES NOT INCLUDE:
- [Scope boundary 1]
- [Scope boundary 2]
For Tim to use at the START of a session to calibrate client expectations.
EXPECTATION-SETTING SCRIPT: [Session Type] with [Client]
──────────────────────────────────────────────────────────
OPEN WITH (say this within first 2 minutes):
"[Exact words Tim should say to set the expectation for this session.
What they'll get, what they won't get, and what happens next.]"
INOCULATE (address transferred expectations):
"[Exact words to preemptively address what they expect based on past
experiences with consultants/tech providers. E.g., 'You've probably
had consultants dump data on you before. That's not what today is.']"
DECLARE THE DELIVERABLE:
"[Exact words naming what they'll walk away with today. Not a feeling —
a thing. E.g., 'By the end of this session, you'll have a one-page
priority map with three things you own and three things to delegate.']"
CHECK AT MIDPOINT:
"[Exact words to verify expectations are being met mid-session.
E.g., 'Before we go further — is this answering the question you
came in with, or do we need to adjust?']"
CLOSE WITH:
"[Exact words that connect what was delivered to what was expected.
Name the next step. Assign ownership. Set timeline.]"
For post-diagnostic sessions where clients are overwhelmed by data.
DIAGNOSTIC TRANSLATION: [Client Name]
Date: [Date] | Prepared by: Tim Lockie, The Human Stack
YOUR SCORES IN PLAIN LANGUAGE:
──────────────────────────────
[Vital 1]: [Score] — What this means: [One sentence, no jargon]
[Vital 2]: [Score] — What this means: [One sentence]
...
THE HEADLINE:
[One sentence summary. E.g., "Your technology is fine. Your people
don't know how to use it together."]
WHAT THIS MEANS YOU SHOULD DO:
1. [Action — not "improve accountability" but "create a weekly 15-min
data review meeting with department leads"]
2. [Action]
3. [Action]
WHAT THIS MEANS YOU SHOULD STOP DOING:
1. [Thing to stop — be specific]
WHAT THESE SCORES DO NOT TELL YOU:
- [Limitation 1]
- [Limitation 2]
BENCHMARKING CONTEXT:
[Where they fall relative to similar orgs — if data available.
If not available, say so explicitly: "We don't have industry
benchmarks yet. Here's what I observe across similar clients:"]
For complex clients who need multiple deliverable types combined.
ENGAGEMENT ROADMAP: [Client Name]
Date: [Date] | Prepared by: Tim Lockie, The Human Stack
ENGAGEMENT TYPE: [Managed Success | Advisory | Custom]
DURATION: [X months]
CADENCE: [Meeting frequency]
PHASE 1: [Name] — Weeks 1-4
─────────────────────────────
GOAL: [What this phase accomplishes]
DELIVERABLES:[What Tim produces]
CLIENT WORK: [What they do between sessions]
EXIT CRITERIA:[How we know this phase is done]
PHASE 2: [Name] — Weeks 5-8
─────────────────────────────
[Same structure]
PHASE 3: [Name] — Weeks 9-12
─────────────────────────────
[Same structure]
EXPECTATIONS TO SET UPFRONT:
- "This will feel [uncomfortable/slow/unclear] during Phase 1. That's normal."
- "You'll see [first signs of progress] around [timeframe]."
- "The biggest risk is [specific risk]. We'll manage it by [specific action]."
- "This engagement does NOT include [scope boundary]. If you need that, here's what it would take."