Lamina flow design
Design reachable actor workflows from typed product operations, dependencies, and terminal outcomes, including complete cross-actor handoffs and recovery.From its SKILL.md
npx -y skills add aryaniyaps/lamina --skill lamina-flow-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
0.9 KB, 148 tokens by cl100k_base, as published. Nobody here has run it
Workflow design
A workflow is a user-reachable sequence of operation.<id> references owned by one actor and ending in named terminal outcomes.
For each critical workflow:
- Name its trigger and
actor_ref. - Reference ordered operations rather than restating them in prose.
- Link dependencies that change reachability.
- Name success, rejection, degraded, and recovery terminal outcomes that materially differ.
- Complete cross-actor handoffs through delivery, recipient binding, accept/reject, durable authority change, both projections, expiry, replay, and recovery.
- Add surfaces only where the workflow needs a user-visible realization.
Do not create a full application flow inventory when only one product slice is being changed.