majiayu000/spellbook / skills/vibeguard
vibeguard
VerifiedLightweight anti-hallucination workflow for task kickoff, review prioritization, and regression retrospectives. Use when the user asks for guardrails, task contracts, risk scoring, or review templates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.8 KB |
| references/review-template.md | markdown | 1.1 KB |
| references/scoring-matrix.md | markdown | 1.9 KB |
| references/task-contract.yaml | config | 1.5 KB |
references/scoring-matrix.md
View on GitHub# Risk Scoring Matrix
Use this matrix to prioritize findings before implementation.
## Dimensions
Score each finding from 1 to 5.
### Impact
- 1: cosmetic or low-value cleanup
- 2: readability or minor developer-experience improvement
- 3: meaningful maintainability or correctness improvement
- 4: affects core behavior, data quality, or reliability
- 5: severe defect, major regression risk, or architecture-level issue
### Effort
- 1: tiny localized edit
- 2: small change across a few files
- 3: medium cross-module change
- 4: large refactor or migration
- 5: broad, high-cost system change
### Risk
- 1: very unlikely to regress
- 2: limited blast radius
- 3: requires targeted verification
- 4: touches critical paths or contracts
- 5: highly sensitive, compatibility-heavy, or hard to roll back
### Confidence
- 1: weak intuition only
- 2: indirect evidence
- 3: partial path or symptom evidence
- 4: strong code, test, or log evidence
- 5: fully traced and reproducible
## Formula
```text
priority_score = (impact * confidence) - (effort + risk)
```
Higher scores should be handled earlier.
## Priority Bands
| Band | Score | Meaning |
|------|-------|---------|
| P0 | 12+ | High-confidence, high-impact work |
| P1 | 4-11 | Valuable and actionable |
| P2 | 0-3 | Cleanup, follow-up, or lower urgency |
| P3 | Below 0 | Do not schedule without stronger evidence |
## Gating Rules
1. High-risk findings do not become P0 without strong evidence.
2. Low-confidence findings stay out of execution plans.
3. Re-score the backlog after major architectural changes.
4. If a fix is risky, add verification before widening scope.
## Template
```markdown
| id | finding | impact | effort | risk | confidence | score | priority |
|----|---------|--------|--------|------|------------|-------|----------|
| F1 | ... | 5 | 2 | 2 | 5 | 21 | P0 |
| F2 | ... | 3 | 3 | 3 | 4 | 6 | P1 |
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |