deviation-rules

Classifies deviations during execution and decides whether to auto-fix or escalate them.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill deviation-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deviation-rules
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/deviation-rules
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill deviation-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deviation handling during plan execution is centralized into a decision framework that classifies each deviation and determines whether to auto-fix (Rules 1-3) or escalate to architectural changes (Rule 4), while logging every deviation for SUMMARY.md.

Core Features & Use Cases

  • Rule-based deviation classification for auto-fix, auto-add missing functionality, blocking issues, and escalation.
  • Deterministic decision flow for executor and CI integration with clear guidance on when to stop for architectural changes.
  • Comprehensive deviation tracking and documentation to support a living SUMMARY.md across phases.

Quick Start

Observe a deviation during task execution and apply the deviation framework to auto-fix or escalate, then record the outcome.

Frequently Asked Questions about deviation-rules

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

FAQPage Schema
How do I handle deviations discovered during plan execution in CI tasks?

Deviation handling during plan execution is centralized into a decision framework that classifies each deviation and determines whether to auto-fix or escalate, while logging every deviation for SUMMARY.md. This ensures consistency and traceability across CI tasks.

What is a structured deviation framework for executor tasks?

A structured deviation framework is a decision flow that classifies deviations to auto-fix missing functionality or blocking issues via Rules 1-3, and escalates architectural changes via Rule 4. It enforces safe decision-making and records outcomes for SUMMARY.md.

When should I escalate deviations instead of auto-fixing them?

You should escalate deviations when they involve architectural changes, specifically classified under Rule 4. The framework provides clear guidance on when to stop for architectural changes, whereas Rules 1-3 cover auto-fixing missing functionality and blocking issues.

How do I track deviations and maintain documentation across project phases?

You track deviations by applying the decision framework which keeps a complete log of all classified deviations and outcomes. This comprehensive deviation tracking supports a living SUMMARY.md document that stays updated across phases.

Can I use rule-based deviation classification for both executor and CI integration?

Yes, the rule-based deviation classification provides a deterministic decision flow designed for both executor and CI integration. It guides behavior for missing functionality, blocking issues, and architectural changes while ensuring actions align with plan goals.