メニュー
Map prerequisite, data, lifecycle, and reachability dependencies between typed product-graph nodes, including explicit behavior when a dependency is unmet.
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.
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.
| name | lamina-dependencies |
| description | Map prerequisite, data, lifecycle, and reachability dependencies between typed product-graph nodes, including explicit behavior when a dependency is unmet. |
Use top-level dependencies[] when one product behavior relies on another node. Dependencies prevent silent happy paths when setup, ownership, state, or another workflow is missing.
{
"id": "accept-requires-live-invite",
"type": "prerequisite",
"from": "workflow.accept-invite",
"to": "entity.invitation",
"required_state": "pending",
"unmet_behavior": "Reject acceptance, explain expiry or prior use, and offer a new invitation path",
"criticality": "critical",
"source": "derived",
"confidence": "high",
"relevance_reason": "The workflow cannot succeed without a pending invitation"
}
from and to references.unmet_behavior; do not use vague precondition prose.risk_key when the unmet behavior materially affects the product.Avoid infrastructure/vendor dependencies unless they alter user-visible product behavior.