decision-rules

Provides a decision table with rationale for resolving ambiguous coding requests and scope conflicts.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/TierOne-Studio/spa-velocity --skill decision-rules-tierone-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-rules
Source: https://github.com/TierOne-Studio/spa-velocity/tree/main/.ruler/skills/decision-rules
Command: npx skills add https://github.com/TierOne-Studio/spa-velocity --skill decision-rules-tierone-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a user request is ambiguous, a test fails unexpectedly, or CLAUDE.md and a skill seem to disagree, AI coding assistants often guess silently or overreach in scope. This Skill supplies a full decision table with per-row rationale so every judgment call under uncertainty follows a documented, defensible default. ## Core Features & Use Cases - Thirteen decision rules with rationale: Covers bug-fix scope, missing test infrastructure, suspicious failing tests, performance and cleanup requests, CLAUDE.md vs skill conflicts, approval ambiguity, confidence scoring, and more. - Explicit overrides and anti-patterns: Each rule states when the default does not apply, plus a list of behaviors to avoid such as silently picking between interpretations or rounding up confidence scores. - Use Case: A user says "make it faster" with no details. Instead of speculatively adding caching, the assistant follows rule 4: profile first, identify the bottleneck, then propose a targeted change with measured impact. ## Quick Start Ask the assistant to apply the decision-rules skill to decide how to handle an ambiguous request like a failing test that looks wrong.

Frequently Asked Questions about decision-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle an ambiguous user request in AI-assisted coding?

Present the reasonable interpretations numbered and let the user pick explicitly, rather than silently choosing one. If the interpretations differ only trivially, implement the recommended one but still surface the alternative as a question.

What should I do when a failing test looks wrong?

Stop and ask before changing anything. The default assumption is that the code regressed and the test asserts the previous correct behavior, since tests rot less often than code. Check git blame history before suspecting the test.

When does a skill override CLAUDE.md guidance?

Follow the skill when it applies, unless applying it forces a structural change such as new dependencies, cross-cutting infrastructure, or refactoring unrelated modules. In that case follow CLAUDE.md for the current PR and recommend the skill's pattern as a future task with an ADR.

Should I fix adjacent bugs while fixing a reported bug?

No. Fix only the named bug surgically and mention the adjacent issue as a follow-up. Bundling fixes makes diffs harder to review and bisect. The exception is when the adjacent issue is the actual cause of the named bug.

When should I not use the decision-rules skill?

Skip it for unambiguous requests, code-quality questions (use design-review instead), and workflow procedures (use plan-mode or tdd-workflow). If the skill triggered but its content does not fit the task, note the misfire rather than force-fitting it.