bvssh-check

Solid

Use to evaluate whether current work aligns with Better Value Sooner Safer Happier. Run at diamond completion and periodically.

AI & Automation 41 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# BVSSH Check Skill Evaluate alignment with Better Value Sooner Safer Happier. ## Workflow For each dimension, assess current state: ### Better - [ ] Quality improving or stable (not degrading)? - [ ] Technical debt under control (not growing unchecked)? - [ ] User satisfaction metrics stable or improving? - [ ] Defect rate stable or declining? - Evidence: [cite specific metrics or observations] ### Value - [ ] Delivering measurable user or business outcomes? - [ ] Outcome metrics moving (not just output metrics)? - [ ] Work aligned with strategic priorities? - [ ] Not shipping features nobody uses? - Evidence: [cite specific metrics or observations] ### Sooner - [ ] Lead time stable or decreasing? - [ ] Batch sizes small? - [ ] WIP limits respected? - [ ] Handoffs minimized? - [ ] No unnecessary waiting or queuing? - Evidence: [cite specific metrics or observations] ### Safer - [ ] Security posture maintained or improved? - [ ] Compliance requirements met? - [ ] Risk being actively managed (not ignored)? - [ ] Rollback capability tested? - [ ] No new single points of failure? - [ ] Error budget healthy? (SRE -- check dora-metrics.yml sre section) - Evidence: [cite specific metrics or observations] ### Happier Smart's Happier covers four stakeholders: **customers, colleagues, citizens, and climate**. "Not 'more for less' at any human or climatic cost." **Colleagues:** - [ ] Team working at sustainable pace? No chronic overtime? (XP -- Beck) - [ ] AI tools helping or ...

Details

Author
haabe
Repository
haabe/mycelium
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

values-check

Pressure-tests a decision, plan, or piece of client-facing work against Clear Measure's core values before you commit to it. Use before finalizing a client proposal, staffing decision, or scope change, when a decision "feels off," or when onboarding a new hire to how decisions get made.

0 Updated today
ClearMeasureLabs
AI & Automation Listed

bs-check

Use before telling a client or stakeholder "this is fixed", before deploying changes to a production site or service, before activating or modifying a live automation/workflow, before claiming an integration works end-to-end, before quoting pricing or API behavior in a comparison, or before running a destructive infrastructure command. Also use when the user says "confidence check", "how confident are you", "validate this", "pressure-test this", "/bs-check", or whenever a confident-sounding claim has not been directly validated by a query, observation, comparison, or quotable source. ALSO covers design-time reasoning audits via subcommands - "bs-check premise" (are we solving the right problem? premise acceptance - Socratic + Steelman), "bs-check approach" (did we commit too fast? - Burden of Proof, Cold Start, Alternatives, Pre-mortem), "bs-check fresh" (all 9 patterns, fresh-context sub-agent). Trigger phrases for those - challenge this, push back, devil's advocate, poke holes, steelman this, are we solving

0 Updated today
GemSpecter
AI & Automation Solid

harms-check

Use when building anything USER-FACING (or with persuasion/retention/cancellation/consent/pricing flows, or that touches vulnerable people) to surface design-level harm the security/privacy/compliance gates miss: dark/deceptive patterns and foreseeable misuse. Assumes the product works as designed and asks who it could harm and whether it is Happier-negative. NUDGE, not a block.

41 Updated today
haabe