plan-confirm

Confirms Hypo-Workflow plans before execution in the P4 Confirm stage.

24|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-confirm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-confirm
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/plan-confirm
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill plan-confirm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a mandatory checkpoint to ensure that generated Hypo-Workflow plans are reviewed and explicitly approved before execution, preventing unintended actions.

Core Features & Use Cases

  • Confirm and gate the planned milestones during the P4 Confirm stage.
  • Surface a concise plan summary (project name, tech stack, preset, milestone count, generated files, and mode).
  • Enforce hard confirmation when gating requires explicit approval and activate the current phase plan_confirm.

Quick Start

Review the generated Hypo-Workflow plan and confirm to proceed with execution in the P4 Confirm stage.

Frequently Asked Questions about plan-confirm

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

FAQPage Schema
How do I add a mandatory checkpoint to confirm a plan before execution starts?

To add a mandatory checkpoint before execution, this skill activates a plan_confirm phase during the P4 Confirm stage, validating the plan mode and enforcing hard user approval when gating rules require it.

What is a plan confirmation gate in a milestone-based workflow?

A plan confirmation gate is a mandatory review checkpoint that surfaces a concise summary of project milestones, tech stack, and generated files, preventing unintended actions by requiring explicit user approval before execution.

How do I review and approve generated milestones during the P4 Confirm stage?

You review and approve milestones during the P4 Confirm stage by examining the surfaced plan summary, which includes project name, preset, milestone count, and generated files, then providing explicit confirmation to proceed with execution.

Does the plan confirmation checkpoint support automation gates and explicit approval rules?

Yes, the plan confirmation checkpoint validates automation gates and enforces hard confirmation rules, ensuring explicit user approval is required when gating conditions demand it before the workflow can proceed.

What details are included in the plan summary surfaced for review before execution?

The plan summary surfaced for review includes the project name, tech stack, preset, milestone count, generated files, and current mode, providing a clear overview to validate before granting execution approval.

Why does my workflow require explicit approval before executing a generated plan?

Your workflow requires explicit approval because the gating rules enforce a mandatory checkpoint to prevent unintended actions, validating the plan mode and demanding user confirmation before transitioning to the execution phase.