stop

Name: stop
Availability: InStock
Author: jonely235

Enforce a four-phase STOP workflow before any code changes.

Updated Dec 30, 2025

Search Tags:#trace #coding #plan #quality-assurance #stop #code-review #orient

Ready to run

npx skills add https://github.com/Jonely235/claude-skills --skill stop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stop
Source: https://github.com/Jonely235/claude-skills/tree/main/stop
Command: npx skills add https://github.com/Jonely235/claude-skills --skill stop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

STOP protocols enforce reading the codebase before coding, preventing premature changes and reducing defects caused by blind coding.

Core Features & Use Cases

STOP provides a four-step workflow (Stop, Trace, Orient, Plan) to structure any code change.
It includes practical guidance, templates, and references to help teams integrate the discipline into reviews and pair programming.

Quick Start

Pause and apply STOP: Stop, Trace, Orient, Plan before you code.

Frequently Asked Questions about stop

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

FAQPage Schema

How do I prevent premature coding when starting a new feature or bug fix?▼

To prevent premature coding, apply the STOP protocol before writing any code. This four-phase workflow enforces reading the codebase first, mitigating hasty changes and reducing defects caused by blind coding across solo and team environments.

What is the STOP protocol workflow for software engineering tasks?▼

The STOP protocol is a four-step workflow: Stop, Trace, Orient, and Plan. It structures any code change by enforcing timeboxed steps and utilizing templates before actual coding begins, ensuring thorough codebase comprehension.

How do I structure a code review to catch defects from blind coding?▼

Structure code reviews by integrating the STOP discipline to enforce reading the codebase before changes. The protocol provides practical guidance and templates to help teams identify blind coding defects during pair programming and reviews.

Does the STOP workflow apply to debugging and refactoring tasks?▼

Yes, the STOP workflow applies to debugging, refactoring, optimizations, new features, and bug fixes. It mitigates premature changes across all these coding tasks by enforcing the Stop, Trace, Orient, Plan phases before any modifications.

What's the best way to enforce a stop-before-code discipline in a development team?▼

The best way to enforce stop-before-code discipline is applying the STOP protocol with timeboxed steps. Teams utilize provided templates and references to integrate this quality-assurance workflow into pair programming and code reviews.

When should I not use a strict trace and plan workflow before coding?▼

The STOP protocol is designed for all code changes including refactors and optimizations, but its timeboxed Stop, Trace, Orient, Plan phases may add overhead for trivial syntax fixes where reading the entire codebase is unnecessary.