safe-execute

Enforce a five-phase gated workflow for complex software changes.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill safe-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-execute
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/reference/content/methodology/templates/skills/safe-execute
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill safe-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents complex software tasks from being implemented prematurely or completed without evidence by enforcing a structured five-phase workflow with explicit validation gates.

Core Features & Use Cases

  • Five-Phase Execution: Clarify the request, create an execution plan, verify alignment with product and visual sources, implement in controlled chunks, and verify the result.
  • Alignment and Safety Gates: Require explicit checks against PRD, canonical designs, implementation plans, invariants, decisions, blockers, and agent responsibilities before implementation begins.
  • Evidence-Based Completion: Validate tests, builds, types, linting, visual review, reviewer findings, and acceptance criteria before declaring the work complete.
  • Use Case: Apply this Skill to a multi-file feature, sprint user story, risky refactor, or change that affects project invariants and requires traceable implementation evidence.

Quick Start

Activate the safe-execute skill for the requested complex task and proceed through all five phases without skipping a gate.

Frequently Asked Questions about safe-execute

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

FAQPage Schema
How do I execute complex multi-file software changes without breaking existing invariants?

Executing complex multi-file changes safely requires a gated workflow that enforces written specifications, verifies alignment with product and design sources, and validates fresh evidence from quality gates before completion.

What is the best way to prevent premature implementation of risky refactors?

Preventing premature implementation of risky refactors involves enforcing a structured five-phase execution plan with explicit safety gates, requiring source verification and delegated implementation in controlled chunks before declaring the work complete.

How do I verify sprint user stories against product requirements before coding?

Verifying sprint user stories against product requirements requires explicit alignment checks against PRDs, canonical designs, implementation plans, and decisions before any implementation begins to ensure full traceability.

When do I need a gated execution workflow for software development tasks?

A gated execution workflow is needed for multi-file features, sprint user stories, invariant-sensitive changes, and risky refactors requiring alignment across product, design, and implementation sources with evidence-based completion.

How do I ensure evidence-based completion for complex feature implementation?

Ensuring evidence-based completion for feature implementation requires validating tests, builds, types, linting, visual review, reviewer findings, and acceptance criteria through quality gates before the task is declared complete.

Can I use safe execution workflows for tasks requiring alignment across product and design?

Safe execution workflows support tasks requiring alignment across product, design, and implementation sources by enforcing explicit verification gates against PRDs and canonical designs before proceeding through the five-phase implementation process.