plan

Convert discovery outputs into a phased development plan with work orders.

2|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/chieflatif/vibeos-plugin --skill plan-chieflatif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/chieflatif/vibeos-plugin/tree/main/plugins/vibeos/skills/plan
Command: npx skills add https://github.com/chieflatif/vibeos-plugin --skill plan-chieflatif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans complex projects by turning validated discovery into a complete development plan with phased work orders and governance setup.

Core Features & Use Cases

  • Converts discovery outputs into a structured plan with defined phases, governance gates, and work orders.
  • Applies the decision engine to derive actionable phases, milestones, and remediation paths from project-definition.json and related docs.
  • Enables end-to-end project execution with traceable governance and a reusable planning template.

Quick Start

Provide your project discovery data and say make a plan to generate a phased development plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn discovery outputs into a structured development plan?▼

To turn discovery outputs into a development plan, provide your project discovery data and trigger the planning process to generate a structured, phased execution plan with defined governance gates and work orders.

What do I need to generate a phased development plan with work orders?▼

You need completed product discovery outputs, specifically a project-definition.json file and related product or architecture docs, to generate a phased development plan with work orders.

Can I use this planning approach for projects at any scale?▼

You can use this planning approach for projects at any scale, provided that product discovery is complete and you require a structured plan with governance setup and an intake-driven workflow.

What is the best way to organize an intake-driven workflow for project execution?▼

The best way to organize an intake-driven workflow is by applying a decision engine to your discovery docs, deriving actionable phases, milestones, and remediation paths for end-to-end project execution.

How does governance setup work when creating a development plan?▼

Governance setup works by enforcing prerequisites and applying governance gates within the generated development plan, ensuring traceable project execution and reusable planning templates from your initial discovery inputs.

When should I not use a phased planning approach for my project?▼

You should not use a phased planning approach if your product discovery is incomplete, as the process strictly enforces prerequisites and requires discovery outputs like project-definition.json to function correctly.