skills.rest
yslee5005
yslee5005COMMUNITY
Explore all skills by this author →
GitHub

decide

Classify incoming requests into decision options and STOP before code changes.

Updated Apr 5, 2026
Search Tags:#workflow#decision#governance#risk-assessment#software-engineering#code-change
One-click install
npx skills add https://github.com/yslee5005/app-library --skill decide-yslee5005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decide
Source: https://github.com/yslee5005/app-library/tree/main/.claude/skills/decide
Command: npx skills add https://github.com/yslee5005/app-library --skill decide-yslee5005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Required process before code modification. Classify the request, present options, then STOP.

Core Features & Use Cases

  • Classify requests into Bug Fix, Feature Decision, Refactoring, or Architecture.
  • Present multiple options for decision-making and halt execution until confirmation.
  • Enforce a STOP rule to prevent any code changes without explicit user action.

Quick Start

Provide decision options for a feature request and STOP before making any code changes.

Frequently Asked Questions about decide

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

FAQPage Schema
How do I enforce a decision gate before making code changes?▼

To enforce a decision gate before code changes, this workflow reads your project boundaries and classifies requests into bug fixes, features, refactors, or architecture changes, then halts execution until you confirm an option.

What is the best way to classify incoming software development requests?▼

The best way to classify incoming software development requests is to analyze target code files and project boundaries, categorizing them as bug fixes, features, refactors, or architecture changes before implementation.

How do I present implementation options for a bug fix or feature request?▼

To present implementation options for a bug fix or feature request, the workflow evaluates the target application and outputs a STOP instruction alongside multiple decision options for team review before execution.

Can I prevent code modifications until a risk assessment is reviewed?▼

Yes, you can prevent code modifications by applying a STOP rule that halts execution immediately after classifying the request and generating decision options, ensuring explicit user action is required to proceed.

Does this workflow require specific project files to function correctly?▼

Yes, this workflow requires reading CLAUDE.md boundary files, the target application's CLAUDE.md, and related code files to accurately classify requests and provide appropriate decision options.

When do I need a governance process for software engineering tasks?▼

You need a governance process for software engineering tasks when teams require structured risk assessment and decision-making prior to implementing bug fixes, features, refactors, or architecture changes.

Related Skills

Explore More Software Engineering Skills→
MartinNevlahaMartinNevlaha
1

governance-db

Retrieve project governance documentation via the stratus MCP retrieve tool.

Community
Basic
GoBeromsuGoBeromsu
2

test-driven-development

Implement a RED-GREEN-REFACTOR workflow to guide code changes with tests.

Community
Advanced
kekemotokekemoto

diff-summary

Generate structured, intent-based summaries of code changes for review.

Community
Basic
insightwavesmithinsightwavesmith

code-analyzer

Analyze code changes to identify those meeting evidence-shape-check criteria.

Community
Intermediate