OpenParable
Skip to content
← Back to skills

Vibe Do It

Others
vibe-do-it

Vibe Do It is an Agent Skill for general use published in the foryourhealth111-pixel/Vibe-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Execute through the full governed path with an implementation-forward bias while keeping canonical vibe as the only governed runtime.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/HEAD/bundled/skills/vibe-do-it/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vibe-do-it, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Use canonical vibe as the only governed runtime authority for this request.

Entry bias:

  • move toward execution
  • retain requirement and plan governance
  • keep verification and cleanup mandatory
  • continue through canonical phase_cleanup

Execution rules:

  • delegate to canonical vibe
  • keep vibe as the only runtime authority
  • let canonical vibe keep router selection and confirm_required ownership
  • do not create a second requirement surface
  • do not create a second plan surface
  • do not create a parallel runtime
  • do not preflight-scan the current workspace or repository for canonical proof files before launch
  • Launch canonical-entry first; validate receipts only after it returns a session root
  • if the latest verified runtime-summary.json exposes bounded_return_control.explicit_user_reentry_required = true, forward --continue-from-run-id <source_run_id> and --bounded-reentry-token <reentry_token> before launching this wrapper

When this wrapper is chosen, bias canonical vibe toward:

  • approved-plan execution
  • plan_execute readiness
  • preserving verification and cleanup gates
  • a bounded terminal stage of phase_cleanup

Request: $ARGUMENTS