Run any Skill in Manus with one click

vibeos-plan

Stars2

Forks1

UpdatedApril 29, 2026 at 17:28

VibeOS planning and work-order generation for Codex. Use when the user says make a plan, break the work down, organize the roadmap, create work orders, or wants governance and sequencing created after discovery.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

chieflatif

chieflatif/vibeos-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	vibeos-plan
description	VibeOS planning and work-order generation for Codex. Use when the user says make a plan, break the work down, organize the roadmap, create work orders, or wants governance and sequencing created after discovery.

VibeOS Plan

Use this skill when discovery is done and the project needs a real development plan.

Workflow

Read:
- project-definition.json
- docs/product/PRD.md
- docs/product/PRODUCT-ANCHOR.md
- docs/product/ARCHITECTURE-OUTLINE.md
- docs/ENGINEERING-PRINCIPLES.md
- docs/research/RESEARCH-REGISTRY.md
- docs/decisions/DEVIATIONS.md
Generate or refresh:
- docs/planning/DEVELOPMENT-PLAN.md
- docs/planning/WO-INDEX.md
- docs/planning/AUDIT-PROTOCOL.md
- docs/planning/AGENT-WORKFLOW.md
- docs/planning/WO-*.md
- .claude/quality-gate-manifest.json
- scripts/architecture-rules.json when architecture enforcement is needed
If the project is a git repo and .claude/quality-gate-manifest.json now exists, install or refresh commit-boundary hooks:
- bash ".vibeos/scripts/setup-git-hooks.sh" --project-dir "."
For midstream projects, create or refresh:
- .vibeos/findings-registry.json
- .vibeos/baselines/midstream-baseline.json
- .vibeos/midstream-report.md
- remediation work orders in Phase 0
Use outcome language first, then technical detail.
Make phase sequencing, dependencies, and acceptance criteria explicit enough for truthful build execution.
When the project needs 24-48 hour autonomy, record that as long-run autonomy in .vibeos/config.json and expect heartbeat, checkpoint, audit cadence, failure-loop detection, recovery planning, evidence-backed recovery resolution, scheduler guarding, and closeout validation via .vibeos/scripts/autonomy-heartbeat.py, .vibeos/scripts/autonomy-failure-detector.py, .vibeos/scripts/autonomy-recovery-planner.py, .vibeos/scripts/autonomy-recovery-resolution.py, .vibeos/scripts/autonomy-scheduler-guard.py, and .vibeos/scripts/validate-long-run-autonomy.py.

Rules

Do not start implementation inside planning.
Do not create a WO without evidence or a concrete objective.
Preserve shared .vibeos/ state so Claude/Cursor and Codex can resume from the same planning base.
Codex does not get Claude runtime hooks; Git hooks are the commit-boundary substitute once planning creates the shared gate manifest.

More from this repository

same repository

audit

chieflatif/vibeos-plugin

Full audit cycle that dispatches audit agents (security, architecture, correctness, test quality, evidence, product drift, flow, system invariants, dependency intelligence, delivery infrastructure, red team, contract validator), applies consensus logic, and produces a composite report with actionable findings. Use when the user says "audit the code", "review everything", "check for security issues", "do a full review", or wants a comprehensive multi-perspective code review.

2026-06-152

build

chieflatif/vibeos-plugin

Autonomous build orchestrator that executes work orders end-to-end. Use when the user says "continue", "keep going", "build the next thing", "resume", "start building", or wants to make progress on the development plan. Dispatches investigator, tester, prompt-engineering, implementation, and documentation agents in sequence with two-layer quality enforcement (Layer 1 gates + Layer 2 audit agents) and error recovery, while checking for product drift and stale high-impact decisions.

2026-06-152

vibeos-audit

chieflatif/vibeos-plugin

VibeOS audit flow for Codex. Use when the user asks for a code audit, quality review, governance review, architecture review, security review, or wants a full audit cycle before or after implementation work.

2026-04-292

vibeos-autonomous

chieflatif/vibeos-plugin

Full autonomous-session override for VibeOS in Codex. Use when the user says go autonomous, stop checking in, run on your own, stay in autonomous mode, or wants VibeOS to keep building until a real blocker or decision appears.

2026-04-292

vibeos-build

chieflatif/vibeos-plugin

Autonomous VibeOS work-order execution for Codex. Use when the user says continue, resume, keep going, build the next thing, start implementing, or wants progress against the current VibeOS plan.

2026-04-292

vibeos-checkpoint

chieflatif/vibeos-plugin

Phase-boundary checkpoint and ratchet review for VibeOS in Codex. Use when the user says phase is done, milestone check, checkpoint this phase, or wants a boundary audit before starting the next phase.

2026-04-292

name	vibeos-plan
description	VibeOS planning and work-order generation for Codex. Use when the user says make a plan, break the work down, organize the roadmap, create work orders, or wants governance and sequencing created after discovery.

VibeOS Plan

Use this skill when discovery is done and the project needs a real development plan.

Workflow

Read:
- project-definition.json
- docs/product/PRD.md
- docs/product/PRODUCT-ANCHOR.md
- docs/product/ARCHITECTURE-OUTLINE.md
- docs/ENGINEERING-PRINCIPLES.md
- docs/research/RESEARCH-REGISTRY.md
- docs/decisions/DEVIATIONS.md
Generate or refresh:
- docs/planning/DEVELOPMENT-PLAN.md
- docs/planning/WO-INDEX.md
- docs/planning/AUDIT-PROTOCOL.md
- docs/planning/AGENT-WORKFLOW.md
- docs/planning/WO-*.md
- .claude/quality-gate-manifest.json
- scripts/architecture-rules.json when architecture enforcement is needed
If the project is a git repo and .claude/quality-gate-manifest.json now exists, install or refresh commit-boundary hooks:
- bash ".vibeos/scripts/setup-git-hooks.sh" --project-dir "."
For midstream projects, create or refresh:
- .vibeos/findings-registry.json
- .vibeos/baselines/midstream-baseline.json
- .vibeos/midstream-report.md
- remediation work orders in Phase 0
Use outcome language first, then technical detail.
Make phase sequencing, dependencies, and acceptance criteria explicit enough for truthful build execution.
When the project needs 24-48 hour autonomy, record that as long-run autonomy in .vibeos/config.json and expect heartbeat, checkpoint, audit cadence, failure-loop detection, recovery planning, evidence-backed recovery resolution, scheduler guarding, and closeout validation via .vibeos/scripts/autonomy-heartbeat.py, .vibeos/scripts/autonomy-failure-detector.py, .vibeos/scripts/autonomy-recovery-planner.py, .vibeos/scripts/autonomy-recovery-resolution.py, .vibeos/scripts/autonomy-scheduler-guard.py, and .vibeos/scripts/validate-long-run-autonomy.py.

Rules

Do not start implementation inside planning.
Do not create a WO without evidence or a concrete objective.
Preserve shared .vibeos/ state so Claude/Cursor and Codex can resume from the same planning base.
Codex does not get Claude runtime hooks; Git hooks are the commit-boundary substitute once planning creates the shared gate manifest.