bundles/startup/skills/startup-icp-definer/SKILL.md
Use this skill when users need to define their ideal customer profile, identify target personas, map buying centers, or understand who they're selling to. Activates for "who is my customer," "define ICP," "target audience," or persona questions.
npx skillsauth add shipshitdev/library startup-icp-definerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help indie founders precisely define who they're building for using Hexa's Opportunity Memo methodology. Execute rigorous customer definition by guiding users through buying center mapping, pain point hierarchies, and validation frameworks.
Hexa's Core Principle: "Define the company type + the buying center people involved in the decision-making process."
┌─────────────────────────────────────────┐
│ BUYING CENTER │
│ (All people in the decision) │
├─────────────────────────────────────────┤
│ USER PERSONA │
│ (Who uses it daily) │
├─────────────────────────────────────────┤
│ BUYER PERSONA │
│ (Who signs the check) │
├─────────────────────────────────────────┤
│ COMPANY PROFILE │
│ (The organization) │
└─────────────────────────────────────────┘
Build from bottom up: Company → Buyer → User → Buying Center.
Score: Urgency + Cost + Frequency + Actively Solving Focus on pains scoring 8+
Before finalizing ICP:
If you can't do this, your ICP isn't specific enough.
idea-validator - Validate the problemmarket-sizer - Size the segmentleads-researcher - Find matching companiesoffer-architect - Design offer for ICPoutbound-optimizer - Write outreachFor complete persona canvases, buying center maps, interview questions, pain hierarchy scoring, fit scoring framework, and output templates, see: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.