land-adopt-expand-blueprint

I've been digging through skill implementations and your land-adopt-expand framework caught my eye—the way you're breaking down market entry strategy into distinct phases feels like it could be genuinely useful for product teams navigating new markets. That said, at an 82 you've got some solid fundamentals, but there's room to tighten up the documentation and make the progression feel less like reading a strategy textbook.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 82/100, solid B-territory. This is graded against Anthropic's best practices for skill design. Your Writing Style is your strongest pillar at 9/10—the voice is clean and professional—but Ease of Use and Utility are dragging down the score. The framework concept is solid, but it reads more like documentation than a callable tool.

What's Working Well

• Writing quality is crisp — Your imperative voice stays consistent throughout, no marketing fluff or second-person narration creeping in. That 9/10 for Writing Style didn't happen by accident.
• Lean, focused structure — At 31 lines, you're not bloating the file with unnecessary references or tangential content. Single-file structure keeps everything accessible.
• Clear conceptual framework — The 5-component breakdown (Stakeholder Matrix, Phase Milestones, Signal Library, Governance Cadence, Action Playbook) gives people a mental model to hang onto.

The Big One: Missing Procedural Workflow

Here's what's holding you back: Your framework lists what should be in a land-adopt-expand strategy, but it doesn't explain how to use it. Right now it reads like a template structure, not a callable blueprint.

The fix: Add a numbered workflow sequence before the component breakdowns. Something like:

Execution Workflow:
1. Map stakeholder roles using the Stakeholder Matrix (identify 3+ decision-makers per phase)
2. Define phase-specific KPIs and success metrics in Phase Milestones
3. Establish signal thresholds (red/yellow/green indicators) in Signal Library
4. Set governance check-ins (monthly, quarterly, etc.) in Governance Cadence
5. Assign specific actions and resources to each milestone

This transforms it from "here's what a good plan looks like" to "here's how to build one." That's a +2 point swing easy, and it directly addresses why someone would invoke this skill rather than just read a strategy blog post.

Other Things Worth Fixing

1. Description needs activation keywords — Your frontmatter says "Template for orchestrating phased motions" but doesn't say when to use it. Add trigger phrases like "land adopt expand blueprint," "customer success plan," "account expansion strategy." Picks up +2 points in Spec Compliance.

2. Zero template examples — You mention a "Success plan table with phases, KPIs, owners, and timelines" but don't show what that actually looks like. Add a sample row: | Land | Establish POC | Product Lead | 30 days | In Progress |. Real examples beat abstract descriptions. +1-2 points.

3. Tighten vague language — "Recommended plays, assets, and enablement per milestone" is business jargon soup. Say "specific actions, resources, and training materials per milestone" instead. Small fix, improves clarity.

4. Add validation checkpoints — No mention of quality gates. Add: "Verify stakeholder coverage (3+ roles minimum per phase), confirm KPIs are quantifiable, validate signal thresholds with data." +1 point, makes it actionable.

Quick Wins

• Biggest payoff first: Add the numbered workflow sequence (+2 points, fixes high-severity usability gap)
• Then: Add trigger phrases to description and one template example (+3 combined points)
• Then: Tighten vague phrases and add validation section (+2 points)

These three moves get you from 82 to 89+, moving from "good framework" to "actually callable skill."

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.