Lamina stakeholder alignment
Multi-actor goal alignment — explicit trade-offs and permission conflicts in contract. Not org politics or workshop facilitation.From its SKILL.md
npx -y skills add aryaniyaps/lamina --skill lamina-stakeholder-alignmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 169 tokens by cl100k_base, as published. Nobody here has run it
Multi-Actor Goal Alignment (agent-native)
Stakeholders = actors in run.json with goals, permissions, and conflicts — not meeting-room politics.
Framework
- List actors and each one's success outcome
- Surface conflicts (student vs admin regenerates ticket; buyer vs seller refund)
- Record resolution in
decisions.mdwith trade-off rationale - Encode permissions in
actorsandworkflows[].dependency_refs/dependencies[]
Anti-patterns
- Alignment theater — workshops without contract updates
- Hidden veto — unstated stakeholder constraint that breaks invariants
Related
Gives 0 of the 12 instructions most operations skills give in 169 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- list actors and each success outcome
- surface conflicts between actors
- record resolutions in decisions.md
- encode permissions in workflows and dependencies
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.