lamina-edge-cases

Solid

Derive distinct product-risk scenarios from operations, dependencies, authority, lifecycles, concurrency, destructive actions, and recovery without generating exhaustive or duplicate edge-case lists.

AI & Automation 65 stars 2 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 79/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
44
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Distinct product risks Use `scenarios[]` for observable behavior that differs from the primary path. One scenario represents one distinct risk; reuse its `risk_key` rather than multiplying equivalent cases across actors and surfaces. Prioritize: - Declared operation failures. - Unmet dependencies. - Forbidden authority or ownership. - Invalid and stale transitions. - Concurrent consequential mutations. - Destructive confirmation and recovery. - External failure that changes product behavior. Every scenario declares `given[]`, `when.operation_ref`, `then[]`, `covers[]`, metadata, and a unique `risk_key`. Acceptance must be externally observable. “Handle gracefully” is not acceptance. Query the workflow closure and add only missing distinct risk Statements. Persona preferences do not become Scenarios unless they reveal a structural, safety, or evidence-backed failure.

Details

Author
aryaniyaps
Repository
aryaniyaps/lamina
Created
3 weeks ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category