القائمة
Business context UX guidance. Use when bootstrapping Lamina for a project; answering business questions UX work needs; updating context after a pivot or scope change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use only when explicitly invoked as lamina-design. Turn an incomplete product idea or brownfield change into a minimum sufficient product behavior graph: actors, entities, operations, workflows, rules, dependencies, decisions, persona perspectives, and distinct risks; then generate an implementation-ready contract.
Use only when explicitly invoked as lamina-init. Turn an incomplete product idea into usable business context and evidence-grounded personas, asking only high-leverage questions and labeling provisional assumptions for later product-graph design.
Product design workflows — domain contracts, implement brief, verify loop. Load via Read or Skill tool when /lamina-* workflows need it.
Use only when explicitly invoked as lamina. Route product design for developers building with AI — design, verify, or direct capability answers.
Use only when explicitly invoked as lamina-verify. Verify a live or brownfield product against its product graph: critical promises, reachable workflows, authority, invariants, state integrity, recovery, accessibility, and contract drift; emit evidence-backed fixes before merge.
Lamina Problem Router — product design at the intersection of UX, product rules, and systems thinking.
| name | lamina-business-context |
| description | Business context UX guidance. Use when bootstrapping Lamina for a project; answering business questions UX work needs; updating context after a pivot or scope change. |
| metadata | {"lamina":{"id":"business-context","problems":["initialize lamina for a project","bootstrap UX context","business goals success metrics scope","business pivot scope change","what problem are we solving for the business","stakeholder goals before UX work"],"related":["lamina-problem-framing","lamina-stakeholder-alignment","lamina-feature-discovery","lamina-competitive-analysis","lamina-research-scoping"]}} |
Establishes and maintains .lamina/business-context.md — the business foundation UX workflows read before ideating, specifying features, or optimizing flows.
Guardrail: UX artifacts only. Do not implement product code or visual styling specs.
Load artifacts.md for file contract, changelog rules, and downstream ownership.
| Mode | Trigger | Behavior |
|---|---|---|
| Establish | No business-context.md, or user requests fresh bootstrap | Frame gate → Evidence (brownfield) → Write → Cast |
| Update | /lamina-init update, or explicit pivot/scope-change language | Read existing → re-run changed sections → merge + changelog |
Apply the linked capability skill's frameworks when writing each section.
| Section | Skills |
|---|---|
| Problem statement | problem-framing, feature-discovery |
| Business goals | stakeholder-alignment, product-behavior |
| Success metrics | quantitative-validation, stakeholder-alignment |
| Scope | stakeholder-alignment, feature-prioritization |
| Users & market | competitive-analysis, user-modeling — prose in business-context; structured cast in personas.json during establish |
| Product posture | platform-posture, product-behavior |
| Constraints | research-scoping, stakeholder-alignment |
| Stakeholders | stakeholder-alignment |
| Risks & unknowns | feature-discovery, research-scoping |
| Research posture | problem-framing, research-scoping |
| Triad check | product-behavior |
| Inferred context (brownfield only) | scan protocol below |
Ask one batch of clarifying questions for empty sections — not a multi-step wizard.
Before writing .lamina/business-context.md or .lamina/personas.json, require enough non-placeholder input for Problem statement, Scope, Users & market, Product posture, and Constraints. If any of those core sections are empty or too vague to support downstream UX work, use the clarify output contract and STOP. Only carry unanswered items into Open questions when the user explicitly refuses, skips, or asks to proceed without answering.
| Level | Meaning |
|---|---|
| high | Direct stakeholder input, recent validated research, or strong doc evidence |
| medium | Reasonable inference from docs or codebase; not yet validated with users |
| low | Assumption — flag assumption — needs validation; note in Open questions |
Do not present low-confidence assumptions as high confidence.
When a section changes, flag downstream artifacts that may need refresh:
| Changed section | May stale |
|---|---|
| Users & market | personas.json — re-run /lamina-design discovery and cast update |
| Scope | prior run.json flows outside new scope; design runs in flight |
| Business goals, success metrics | audit prioritization; design workflow metrics sections |
| Product posture, constraints | design workflow IA and interaction sections |
| Problem statement (pivot) | personas, prior runs, requirements |
Never silently overwrite personas.json or decisions.md. Offer explicit refresh or append.
Use when shipped UI or product docs exist. Informs business answers, Inferred context section, and provisional persona cast.
docs/, PRDs, pitch decks, marketing copyevidence.mdEvery inferred claim cites @path or states insufficient detail — cannot verify.
Skip scan. Rely on user input and any attached PRD/README.
The section names in the Section → skill mapping are the canonical artifact contract. Write each as its own level-two heading exactly: Problem statement, Business goals, Success metrics, Scope, Users & market, Product posture, Constraints, Stakeholders, Risks & unknowns, Research posture, and Triad check. Additional sections may follow, but must not replace, rename, or combine these headings. Before returning success, validate every canonical section has a non-placeholder **Answer:** line.
---
lamina:
maturity: brownfield # greenfield | brownfield
platform: [web]
last_updated: 2026-07-06
---
# Business context
## Problem statement
**Answer:** …
**Confidence:** medium
**Evidence:** user input
**Skill:** lamina-problem-framing
## Business goals
…
## Changelog
### YYYY-MM-DD — short label
- Changed: …
- Trigger: …
- Stale: …
| Signal | Suggest |
|---|---|
| Problem unclear, early exploration | /lamina-design |
| Specific capability to specify | /lamina-design |
| Shipped UI, known pain, clear goals | /lamina-verify |
| Business context incomplete | finish open questions before other commands |
Do not persist recommendation in any file.