50-execute-gated-150
[50] EXECUTE. Execute plans step-by-step with confirmation gates. Each step requires user approval before proceeding. Includes change management lifecycle (Pre-Change → During → Post-Change → Rollback). Use when implementing approved plans, deploying changes, or any multi-step execution requiring control and reversibility.
Best use case
50-execute-gated-150 is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
[50] EXECUTE. Execute plans step-by-step with confirmation gates. Each step requires user approval before proceeding. Includes change management lifecycle (Pre-Change → During → Post-Change → Rollback). Use when implementing approved plans, deploying changes, or any multi-step execution requiring control and reversibility.
Teams using 50-execute-gated-150 should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/50-execute-gated-150/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 50-execute-gated-150 Compares
| Feature / Agent | 50-execute-gated-150 | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
[50] EXECUTE. Execute plans step-by-step with confirmation gates. Each step requires user approval before proceeding. Includes change management lifecycle (Pre-Change → During → Post-Change → Rollback). Use when implementing approved plans, deploying changes, or any multi-step execution requiring control and reversibility.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Execute-Gated 150 Protocol **Core Principle:** Execute with control. Every step gets a gate — confirm before proceeding. Build in rollback points. Maintain audit trail. ## What This Skill Does When you invoke this skill, you're asking AI to: - **Execute step-by-step** — One atomic action at a time - **Gate every step** — Get confirmation before next step - **Manage change lifecycle** — Pre/During/Post/Rollback phases - **Stay reversible** — Every step can be undone - **Adapt dynamically** — Pause, research, or replan when needed ## The 150% Execution Rule | Dimension | 100% Core | +50% Enhancement | |-----------|-----------|------------------| | **Steps** | Execute sequence | + Atomic, reversible actions | | **Gates** | Get confirmation | + Offer Continue/Pause/Research/Replan | | **Documentation** | Log actions | + Full audit trail | | **Rollback** | Have revert plan | + Pre-identified safe points | ## When to Use This Skill - **Implementing approved plans** — After action-plan-150 - **Deploying changes** — Code, config, infrastructure - **Multi-step operations** — Migrations, refactoring - **High-risk executions** — Where mistakes are costly - **When user needs control** — They decide pace and direction ## Execution Protocol ### Step 1: ACTIVATE Declare execution mode and current state: ``` ⚙️ **Gated-Exec 150 Activated** **Plan:** [What we're executing] **Total Steps:** [N] **Current Phase:** [1 of N] **Rollback Points:** [Where we can safely stop] ``` ### Step 2: PRE-CHANGE Before each step: - Verify prerequisites met - Backup current state if needed - Validate change safety - Confirm readiness ### Step 3: EXECUTE Single atomic step: - Execute one reversible action - Monitor for immediate issues - Document what was done ### Step 4: VALIDATE After each step: - Check completion - Verify expected outcomes - Flag any anomalies ### Step 5: GATE Present decision point: ``` ✅ **Step [X/N] Complete** **Action:** [What was done] **Result:** [Outcome] **Next:** [What's coming] **Options:** - **Continue** → Proceed to next step - **Pause** → Stop for clarification - **Research** → Need more investigation - **Replan** → Strategy needs modification - **Rollback** → Revert to safe point ``` ## Change Management Lifecycle ``` 🔄 CHANGE LIFECYCLE PRE-CHANGE (Before each step) ├── Impact analysis complete ├── Risk assessment done ├── Backup strategy ready └── Rollback plan documented DURING CHANGE (Execution) ├── Atomic step execution ├── Real-time monitoring ├── Immediate issue detection └── Progress tracking POST-CHANGE (After each step) ├── Outcome verification ├── Integration testing ├── Performance validation └── Documentation update ROLLBACK READY (Always) ├── Safe reversal path ├── State restoration ├── Impact minimization └── Lesson documentation ``` ## Decision Gates | Situation | Action | Reason | |-----------|--------|--------| | **Step Success** | Get confirmation, proceed | Maintain control | | **Minor Issue** | Document, continue with caution | Don't stop for small problems | | **Major Problem** | Pause, investigate, possibly rollback | Prevent cascading failures | | **Plan Deviation** | Replan with user approval | Maintain strategic alignment | | **New Information** | Research, update plan | Adapt to new insights | ## Output Format During execution: ``` ⚙️ **Gated-Exec: Step [X/N]** **Phase:** [Current phase name] **Action:** [What we're doing] [Execution details...] **Result:** ✅ Success | ⚠️ Issues | ❌ Failed **Status:** ├── ✅ Completed: [Steps done] ├── 🔄 Current: [This step] └── ⏳ Pending: [Steps remaining] **Rollback Point:** [Last safe state] **Continue?** (Yes / Pause / Research / Replan / Rollback) ``` ## Operational Rules 1. **ATOMIC STEPS:** Each step must be reversible and testable 2. **GATE REQUIRED:** No proceeding without user confirmation 3. **DOCUMENT EVERYTHING:** Full audit trail of all actions 4. **FLEXIBLE ADAPTATION:** Can return to research/planning anytime 5. **CHANGE LIFECYCLE:** Always use Pre/During/Post/Rollback phases 6. **USER CONTROL:** User decides pace and direction ## Failure Modes & Recovery | Failure | Detection | Recovery | |---------|-----------|----------| | **Phase Skipping** | No confirmation obtained | Return to skipped gate | | **Poor Documentation** | Missing audit trail | Document current state, continue with logging | | **Change Cascades** | Unexpected side effects | Rollback to safe point, investigate | | **Loss of Control** | Process confusion | Emergency pause, status assessment | ## Examples ### ❌ Without Gated-Exec ``` User: "Deploy the new feature" AI: [Deploys all 5 steps without confirmation] Result: Breaking change deployed, emergency rollback needed ``` ### ✅ With Gated-Exec 150 ``` User: "Deploy the new feature" ⚙️ Gated-Exec 150 Activated Plan: Feature deployment Total Steps: 5 Rollback Points: After step 2, After step 4 --- ⚙️ Gated-Exec: Step 1/5 Phase: Database Migration Action: Run migration script [Migration executed successfully] Result: ✅ Success - 3 tables updated - No data loss - Backup created Continue? (Yes/Pause/Research/Replan/Rollback) User: "Yes" ⚙️ Gated-Exec: Step 2/5 ... ``` ## Relationship to Other Skills - **action-plan-150** → Creates the plan - **gated-exec-150** → Executes the plan with control - **integrity-check-150** → Validates after completion ## Session Log Entry (MANDATORY) After completing this skill, write to `.sessions/SESSION_[date]-[name].md`: ``` ### [HH:MM] Execute-Gated 150 Complete **Plan Executed:** <plan name> **Steps Completed:** <X/N> **Outcome:** <Success/Rolled Back> **Artifacts:** <files changed> ``` --- **Remember:** Gated execution isn't slow — it's safe. The gates prevent costly mistakes and keep you in control. Every "Yes" is a conscious decision, every step is reversible.
Related Skills
execute
Execute tasks with velocity and quality. Use when ready to implement after clarity and prioritization are complete. This is the fourth system in the 5-system framework.
52-execute-refactor-150
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.
kata-execute-quick-task
Execute small ad-hoc tasks with Kata guarantees, running quick tasks without full planning, or handling one-off work outside the roadmap. Triggers include "quick task", "quick mode", "quick fix", "ad-hoc task", "small task", and "one-off task".
51-execute-quality-150
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
8bit-docs-patterns
Create documentation with gaming-specific examples, retro styling, and 8-bit terminology. Apply when documenting gaming blocks, RPG components, or retro-styled UI elements.
1k-new-skill
Creates a new Claude Code Skill following best practices. Use when the user wants to create a new skill, add a skill, or asks about writing skills for Claude Code. Fetches latest documentation before generating skill content. New skill. Create a skill.
zotero-literature-verification
Complete workflow for verifying academic literature citations using Zotero MCP with full PDF reading and token management
zerubbabel-devops
Provides expert DevOps analysis, CI/CD pipeline review, and infrastructure assessment. Use this skill when the user needs deployment pipeline evaluation, infrastructure review, or platform engineering guidance. Triggers include requests for DevOps audit, CI/CD review, deployment strategy assessment, or when asked to evaluate infrastructure patterns. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
zeabur
Zeabur cloud platform assistant for deployment, management, and optimization. Use when: (1) Deploying applications to Zeabur (Git, Docker, local upload, templates), (2) Managing Zeabur services via CLI (npx zeabur) or GraphQL API, (3) Configuring domains, environment variables, networking, or volumes, (4) Troubleshooting deployment failures, connectivity issues, or build errors, (5) Optimizing Zeabur costs, performance, or high availability architecture, (6) Working with Zeabur templates (YAML spec creation and deployment), (7) Setting up CI/CD pipelines with Zeabur, (8) Managing databases and prebuilt services on Zeabur, (9) Any mention of zeabur, zeabur.yaml, zbpack, zeabur.app, or zeabur CLI commands. Triggers: zeabur, deploy to zeabur, zeabur cli, zeabur api, zeabur template, zbpack, zeabur.app, zeabur domain, zeabur variable, zeabur service.
yaml-validator
Comprehensive YAML syntax validation, error fixing, and schema validation for various formats (GitHub Actions, Docker Compose, Kubernetes, GitLab CI). Use when Claude needs to: (1) Validate YAML syntax, (2) Check YAML files for errors, (3) Fix common YAML formatting issues, (4) Validate against schemas like GitHub Actions workflows, Docker Compose files, Kubernetes manifests, or GitLab CI pipelines, (5) Debug YAML parsing errors. Triggers on phrases like "check yaml", "validate yaml", "fix yaml errors", "yaml syntax".
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment