workflow

Enforce phased analysis, planning, implementation, and validation gates for code changes.

7|2|Updated Dec 10, 2025

Search Tags:#workflow #planning #testing #development #validation #code-review #context-management

Ready to run

npx skills add https://github.com/sbusso/claude-system --skill workflow-sbusso

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, repeatable process to prevent ad-hoc coding, reduce regressions, and ensure changes are planned, implemented, and validated with gates to avoid unchecked architectural drift or incomplete verification.

Core Features & Use Cases

Phase-driven Process: Enforces Analysis, Planning, Implementation, and Validation phases so work is decomposed and reviewed before major changes.
Gated Verification: Requires explicit acknowledgment gates, test runs, type checks, and linting to pass before completion.
Context Awareness: Monitors context usage thresholds and prescribes handoff or scaling actions when context limits are reached; useful for feature work, bug fixes, refactors, and build tasks.

Quick Start

Use the workflow skill to plan, implement, and validate a small feature using the four-phase process.

Frequently Asked Questions about workflow

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

FAQPage Schema

How do I enforce structured development phases for implementing features and fixing bugs?▼

You can enforce structured development phases by applying a process that requires explicit analysis, planning, implementation, and validation gates before code changes are completed. This prevents ad-hoc coding and reduces regressions.

What is the best way to prevent architectural drift during code refactoring?▼

The best way to prevent architectural drift is to use a gated verification process that requires explicit acknowledgment, test runs, type checks, and linting to pass before completing refactoring tasks across repositories and pull requests.

How do I manage context limits when working on large software engineering tasks?▼

To manage context limits during development, you can monitor context usage thresholds and trigger prescribed handoff or scaling actions when limits are reached, ensuring feature work and build tasks remain context-aware.

Does this phased development process work for both small features and large refactoring tasks?▼

Yes, the phased development process applies to software engineering tasks of varying scales, including implementing small features, fixing bugs, and executing large refactors across repositories and pull requests.

What validation checks are required before completing a software implementation?▼

Required validation checks include running tests, type checking, and linting to pass explicit gates, ensuring changes are fully verified before completion to avoid incomplete verification.

Why should I use a phase-driven process instead of ad-hoc coding for software development?▼

A phase-driven process ensures work is decomposed and reviewed before major changes, providing a clear, repeatable method to prevent ad-hoc coding, reduce regressions, and avoid unchecked architectural drift.