Calculates context-appropriate quality gate thresholds based on work type (Feature/Bug/Hotfix/Docs/Refactor). Ensures rigorous standards for features, pragmatic standards for hotfixes, and 100% test pass rate for all work.
Calculates work-specific quality gates (percentage/score targets) for each workflow phase based on work type (Feature/Bug/Hotfix/Documentation/Refactoring). Use at workflow start to set expectations and at phase transitions to validate progress against type-appropriate rigor levels.
/plugin marketplace add DarkMonkDev/WitchCityRope/plugin install darkmonkdev-witchcityrope-agents@DarkMonkDev/WitchCityRopeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Purpose: Calculate appropriate quality gates based on work type and phase.
When to Use: At workflow start to set expectations, and at phase transitions to validate progress.
Executable Script: execute.sh
# Basic usage
bash .claude/skills/quality-gate-calculator/execute.sh <work-type> <phase>
# Examples:
bash .claude/skills/quality-gate-calculator/execute.sh Feature 3
bash .claude/skills/quality-gate-calculator/execute.sh Hotfix 1
bash .claude/skills/quality-gate-calculator/execute.sh Bug 4
Parameters:
work-type: Feature|Bug|Hotfix|Documentation|Refactoring (required)phase: 1|2|3|4|5 (required)Script outputs:
Exit codes:
Not all work is equal:
Universal Rule: ALL work types require 100% test pass rate in Phase 4.
| Work Type | Required % | Score Target | Rationale |
|---|---|---|---|
| Feature | 95% | 24/25 points | Complete requirements critical for feature success |
| Bug Fix | 80% | 20/25 points | Focus on problem and fix, less ceremony |
| Hotfix | 70% | 18/25 points | Emergency - just enough to understand issue |
| Documentation | 85% | 21/25 points | Clear purpose and scope needed |
| Refactoring | 90% | 23/25 points | Understand current state and goals |
| Work Type | Required % | Score Target | Rationale |
|---|---|---|---|
| Feature | 90% | 32/35 points | Thorough design prevents implementation issues |
| Bug Fix | 70% | 25/35 points | Focus on fix design, skip elaborate specs |
| Hotfix | 60% | 21/35 points | Quick design - enough to implement safely |
| Documentation | 80% | 28/35 points | Structure and organization plan |
| Refactoring | 85% | 30/35 points | Detailed refactoring plan with safety checks |
| Work Type | Required % | Score Target | Rationale |
|---|---|---|---|
| Feature | 85% | 43/50 points | High code quality for new features |
| Bug Fix | 75% | 38/50 points | Focus on fix, tests, and no regressions |
| Hotfix | 70% | 35/50 points | Working fix with minimal tests |
| Documentation | 80% | 40/50 points | Complete documentation with examples |
| Refactoring | 90% | 45/50 points | Highest quality - no behavior changes allowed |
| Work Type | Required % | Test Pass Rate | Rationale |
|---|---|---|---|
| Feature | 100% | 100% | ALL tests must pass |
| Bug Fix | 100% | 100% | ALL tests must pass |
| Hotfix | 100% | 100% | ALL tests must pass |
| Documentation | 100% | 100% | ALL tests must pass |
| Refactoring | 100% | 100% | ALL tests must pass |
CRITICAL: Phase 4 is ZERO TOLERANCE for all work types. One failing test = cannot advance.
| Work Type | Required % | Score Target | Rationale |
|---|---|---|---|
| Feature | 80% | 80/100 points | Complete documentation and cleanup |
| Bug Fix | 75% | 75/100 points | Document fix and lessons learned |
| Hotfix | 70% | 70/100 points | Basic documentation, commit, deploy |
| Documentation | 90% | 90/100 points | Comprehensive docs and cross-references |
| Refactoring | 85% | 85/100 points | Document changes and performance impact |
Use the quality-gate-calculator skill to set quality gates for this feature work
# Calculate quality gate for bug fix in design phase
bash .claude/skills/quality-gate-calculator.md Bug 2
# Calculate for hotfix in implementation
bash .claude/skills/quality-gate-calculator.md Hotfix 3
# Phase validator loads quality gate
source /tmp/quality-gate.env
echo "Required: $REQUIRED_PERCENTAGE%"
echo "Target: $TARGET_SCORE / $MAX_SCORE"
Start Workflow
|
v
Identify Work Type
|
+-- Is it production emergency? --> Hotfix (70-100%)
|
+-- Is it fixing existing bug? --> Bug Fix (75-100%)
|
+-- Is it new functionality? --> Feature (85-100%)
|
+-- Is it improving code? --> Refactoring (85-100%)
|
+-- Is it documentation? --> Documentation (80-100%)
v
Calculate Quality Gates for Each Phase
v
Store in Workflow Context
v
Apply at Each Phase Validation
Characteristics:
Examples:
Characteristics:
Examples:
Characteristics:
Examples:
Characteristics:
Examples:
Characteristics:
Examples:
Each phase validator loads work type-specific quality gates:
#!/bin/bash
# In phase-1-validator.md
# Load quality gate for this work type
source /tmp/quality-gate.env
# Use in validation
if [ "$PERCENTAGE" -ge "$REQUIRED_PERCENTAGE" ]; then
echo "✅ PASS - Meets quality gate"
else
echo "❌ FAIL - Below quality gate"
echo " Required: $REQUIRED_PERCENTAGE%"
echo " Actual: $PERCENTAGE%"
fi
Problem: Feature classified as bug fix to lower quality gates Impact: Lower quality work slips through Solution: Orchestrator validates work type at workflow start
Problem: Developer tries to lower requirements Impact: System integrity compromised Solution: Quality gates are non-negotiable per work type
Problem: Everything labeled "hotfix" to skip rigor Impact: Production quality degrades Solution: Hotfix requires prod issue ticket + approval
{
"qualityGate": {
"workType": "Feature",
"phase": 3,
"phaseName": "Implementation",
"required": {
"percentage": 85,
"score": 43,
"maxScore": 50
},
"rationale": "Features require high code quality for new features",
"criticalRules": [
"Phase 4 requires 100% test pass rate regardless of work type"
],
"exported": "/tmp/quality-gate.env"
}
}
Initial Context: Show work type and required percentage only On Request: Show full matrix with rationale During Validation: Show pass/fail threshold On Failure: Show how far from target and what's needed
Remember: Quality gates ensure appropriate rigor for the work being done. Features get highest scrutiny, hotfixes get pragmatic validation, but ALL work requires 100% test pass rate. This balances quality with velocity.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.