advance

Advance a VibeFlow project to the next SDLC phase via MCP.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mytechsonamy/VibeFlow --skill advance-mytechsonamy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advance
Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/advance
Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill advance-mytechsonamy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Advances a project through the SDLC by moving to the next phase while validating current status and recording operator-provided overrides when approvals are required.

Core Features & Use Cases

  • Orchestrates phase transitions by reading vibeflow.config.json, invoking the sdlc_advance_phase MCP tool, and surfacing the resulting state and any pass/fail reasons.
  • Supports HUMAN_APPROVAL_REQUIRED workflows with an optional humanOverrideNote to document the justification for an override.
  • Provides a safe, auditable path to progress from REQUIREMENTS to DEPLOYMENT while preserving a clear audit trail.

Quick Start

Run a command to advance to the next or a specific phase, for example by issuing /vibeflow:advance DESIGN with an optional humanOverrideNote.

Frequently Asked Questions about advance

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

FAQPage Schema
How do I advance an SDLC phase while preserving an audit trail in VibeFlow?

To advance an SDLC phase, the Skill reads vibeflow.config.json to validate the projectId and calls the sdlc_advance_phase MCP tool with the target phase and optional humanOverrideNote to preserve a clear audit trail.

Can I override a HUMAN_APPROVAL_REQUIRED gate during a phase transition?

Yes, you can override HUMAN_APPROVAL_REQUIRED workflows by supplying an optional humanOverrideNote to document the justification for the operator-provided override during the phase transition.

What is needed to progress a project from REQUIREMENTS to DEPLOYMENT with phase guardrails?

Progressing from REQUIREMENTS to DEPLOYMENT requires a validated projectId from vibeflow.config.json and calling the sdlc_advance_phase MCP tool with the target phase to ensure safe, gated phase progression.

How do I trigger a phase transition to a specific SDLC stage like DESIGN?

You trigger a phase transition to a specific stage by issuing the advance command with the target phase name, such as DESIGN, along with any required humanOverrideNote for approval workflows.

Does the SDLC phase advance workflow validate current project status before transitioning?

Yes, the SDLC phase advance workflow validates the current project status by reading vibeflow.config.json and gating phase progression through the sdlc_advance_phase MCP tool to ensure safe transitions.

Why does an SDLC phase transition fail without a humanOverrideNote?

An SDLC phase transition fails without a humanOverrideNote when the current workflow has a HUMAN_APPROVAL_REQUIRED status, meaning operator-provided justification must be recorded to document the override.