Product layer

Skill BTN101/claude-skill-pack/skills/layers/product-layer

Claude skills organized into domain layers — engineering, product, founder/GTM, design, and documents

Install

npx -y skills add BTN101/claude-skill-pack --skill product-layer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Activate this skill group for any product strategy, product thinking, or decision-making task. Triggers include: should I build this, is this a good idea, what should I prioritize, customer discovery, user research, interview questions, validate my idea, product market fit, what's the MVP, feature prioritization, roadmap, user story, PRD, product requirements, jobs to be done, what problem does this solve, why would someone pay for this, retention, engagement loop, habit formation, users aren't coming back, what metrics matter, sprint planning, and any request where the question is about WHAT to build or WHY before getting into HOW. Also use when pressure-testing Antibody or SchoolOrder's product direction.

SKILL.md

4.0 KB, as published. Nobody here has run it

Product Layer

This group covers the full product thinking stack: from raw idea validation through discovery, prioritization, spec writing, and retention design. When activated, identify the right sub-skill and follow its workflow.

Skill Map

Idea Validation (Start Here for Any New Feature or Pivot)

product-lens — founder-style diagnostic. Asks the hard questions: who is this for, what's the pain, why now, what's the MVP, what's the anti-goal, how do you know it's working. Use before building anything new.
lean-startup — Build-Measure-Learn loop, validated learning experiments, pivot-or-persevere decisions, innovation accounting. Use when deciding whether to continue a direction or change it.
37signals-way — build less, fixed time/variable scope, six-week cycles, appetite vs estimates. Use when scoping work or deciding what to cut.

Customer Discovery

mom-test — interview rules that prevent false positives: discuss their life not your idea, ask about specifics in the past, talk less. Use when preparing customer discovery interview questions or interpreting feedback.
discovery-interview-prep — structured interview plan with goal, segment, constraints, and method. Use when preparing to talk to accounting firms or school admins for Antibody/SchoolOrder.
jobs-to-be-done — uncover functional, emotional, and social jobs customers are hiring the product for. Use when repositioning or improving messaging.

Prioritization & Roadmap

prioritization-advisor — RICE, ICE, value/effort scoring. Use when choosing between competing features or deciding what to work on next.
opportunity-solution-tree — maps outcomes → opportunities → solutions → experiments. Use when a stakeholder request needs problem framing before building starts.
problem-framing-canvas — MITRE-style problem statement before jumping to solutions. Use when the problem itself feels fuzzy.

Specs & Documentation

prd-development — PRD that connects problem, users, solution, and success criteria. Use when a feature needs to become an engineering-ready document.
to-prd — turns conversation context into a PRD and pushes it to the issue tracker. Use after a product discussion to capture decisions.
to-issues — breaks a plan or PRD into independently-grabbable issues. Use when turning a spec into actual development tickets.
user-story — Mike Cohn format with Gherkin acceptance criteria. Use when writing development-ready stories.

Retention & Engagement

hooked-ux — Hook Model: Trigger → Action → Variable Reward → Investment. Use when designing engagement loops, notification strategies, or retention mechanics for SchoolOrder or Antibody.

How to Use

Before building: product-lens → lean-startup (in that order) to validate the why.
Before talking to customers: mom-test → discovery-interview-prep.
When choosing what to build: prioritization-advisor → opportunity-solution-tree.
Once decided: prd-development → to-issues to go from idea to tickets.
For retention problems: hooked-ux to design the loop.

The Key Question

Before any feature gets built, answer: "What behavior changes in a real user if this works?" If you can't answer that concretely, go back to product-lens.