vibeos-plan

Generate development plans and work orders from Codex discovery artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VibeOS planning and work-order generation for Codex helps turn discovery outputs into a concrete development plan and actionable work orders, enabling governance and orderly execution.

Core Features & Use Cases

  • Read project inputs from discovery artifacts (project-definition.json, PRD, ARCHITECTURE-OUTLINE.md, ENGINEERING-PRINCIPLES.md, RESEARCH-REGISTRY.md, DEVIATIONS.md) and generate planning outputs.
  • Produce planning artifacts such as DEVELOPMENT-PLAN.md, WO-INDEX.md, AUDIT-PROTOCOL.md, AGENT-WORKFLOW.md, and WO-*.md; set up or refresh .claude quality gates and architecture rules when needed.
  • If the project is a git repo and a quality gate manifest exists, install or refresh commit-boundary hooks using the provided script.
  • For midstream projects, create or refresh findings registry and baselines and generate remediation work orders.
  • Preserve and reuse a shared planning state so Claude/Cursor and Codex can resume from the same base.

Quick Start

Describe your project goals and discovery results, then ask vibeos-plan to generate the development plan and associated work orders.

Frequently Asked Questions about vibeos-plan

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

FAQPage Schema
How do I generate a development plan and work orders from project discovery outputs?

You can generate a development plan and work orders by feeding discovery artifacts like project-definition.json and architecture outlines into the skill, which then outputs DEVELOPMENT-PLAN.md, WO-INDEX.md, and WO-*.md files to structure Codex execution.

What is a work order index and how does it help govern Codex-driven development?

A work order index, or WO-INDEX.md, is a generated registry that sequences actionable work orders for Codex projects, providing governance by organizing development tasks into trackable, auditable units that ensure orderly project execution.

How do I create an audit protocol for development work orders?

To create an audit protocol for work orders, the skill processes your discovery artifacts and automatically generates an AUDIT-PROTOCOL.md file, establishing the review boundaries and quality checks needed for governed Codex execution.

Does vibeos-plan work with existing git repositories and quality gate manifests?

Yes, vibeos-plan works with git repositories by installing or refreshing commit-boundary hooks when a quality gate manifest is present, ensuring that generated work orders align with established codebase governance checks.

What's the best way to plan remediation work orders for a midstream development project?

The best way to plan remediation work orders for midstream projects is to use the skill to create or refresh a findings registry and baselines, which then generates targeted remediation work orders based on the current project state.

Can I resume planning and work order generation from a shared state across Claude, Cursor, and Codex?

Yes, you can resume planning from a shared state because the skill preserves and reuses planning artifacts, allowing Claude, Cursor, and Codex to resume execution from the same baseline configuration and generated work orders.