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