Frame product problems and decide what to build. Use when establishing business context, aligning actors with conflicting goals, discovering or prioritizing features, defining traceable requirements, comparing consequential tradeoffs, or recording a product decision. Use lamina-ux for interaction details and lamina-product-behavior for authoritative runtime rules.
npx skills add https://github.com/aryaniyaps/lamina --skill lamina-product-discovery
decision materially changes the answer; do not preload the directory.
Using lamina-product-discovery: <topic path(s)> sothe selected decision lens is auditable.
| Decision signal | Read | Adds |
|---|---|---|
| Need to turn a vague request into a bounded problem and explicit non-goals | Problem Framing | actors, outcomes, domain boundary, and blocking unknowns |
| Need to establish or update the product's business foundation | Business Context | evidence-backed context artifact, assumptions, and changelog |
| Need to reconcile goals, permissions, or conflicts across multiple actors | Multi-Actor Goal Alignment | explicit conflict resolution and authority mapping |
| Need to derive candidate product behavior from an outcome or user ask | Feature Discovery | entities, operations, workflows, and clarify gates |
| Need to choose which workflows or risks belong in the current slice | Scope Prioritization | invariant-, actor-, dependency-, and verification-aware priority |
| Need to express accepted scope as testable product behavior | Requirements Definition | promises, graph nodes, scenarios, and traceability |
| Need to classify assumptions, policy forks, or high-consequence choices | Product Decisions and Tradeoffs | reversibility, provenance, confidence, and blocking rules |
| Need to rank findings or decide whether a change targets product or contract | Decision Making | impact filter, fix target, and next-action ordering |
Use the smallest sufficient reference set. Common sequences are problem framing
then feature discovery, and tradeoffs then decision making. Business Context is
for establishing or updating the durable foundation, not every feature choice.
Preserve permissions, states, failures, recovery, relationships, and evidence
limits.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take aryaniyaps/lamina-product-discovery from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.