vibe-planning

Convert explicit requirements into a formal implementation plan artifact.

Updated Mar 1, 2026

Search Tags:#workflow #planning #specification #requirements #plan #artifact

Ready to run

npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibe-planning
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-planning
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert vague user intent into a concrete implementation plan.

Core Features & Use Cases

Spec-driven planning: transforms explicit requirements, approval evidence, specifications, acceptance criteria, or task lists into a bounded plan artifact.
Plan-only boundary: ensures only plan artifacts are created or updated until approval, without code, tests, or config edits.
Evidence and risk management: integrates gates, risk tracking, and plan-boundary controls to manage uncertainties.
Output artifacts: produces clear plan documents and future handoff for execution.

Quick Start

Provide explicit planning input (a requirements spec, approval evidence, or concrete inputs) and ask vibe-planning to generate the implementation plan artifact.

Frequently Asked Questions about vibe-planning

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

FAQPage Schema

How do I convert vague project requirements into a concrete implementation plan?▼

A specification-driven planning tool transforms explicit requirements and approval evidence into a bounded plan artifact by enforcing a plan-only boundary, ensuring no code or config edits occur until the formal plan is produced and approved.

How do I generate a formal plan artifact with acceptance criteria before coding starts?▼

To generate a formal plan artifact with acceptance criteria, you input explicit requirements or task lists to produce a bounded plan document that includes tests, risk tracking, and a proceed condition for execution handoff.

Can I use spec-driven planning to block coding until a plan is approved?▼

Yes, spec-driven planning blocks coding until approval by enforcing a plan-only boundary that prevents creating or updating code, tests, or configuration edits until the formal plan artifact is generated.

What is the best way to manage risks and uncertainties during the requirements planning phase?▼

The best way to manage risks during the requirements planning phase is to use a workflow that integrates evidence gates, risk tracking, and plan-boundary controls to manage uncertainties before producing the final execution handoff.

Does vibe-planning support execution handoff with a proceed condition for development teams?▼

Yes, vibe-planning supports execution handoff by outputting a formal plan artifact that defines acceptance criteria, tests, and a specific proceed condition to guide downstream development teams after plan approval.