Convert high-level goals into a deterministic planning DAG for OmegaOS.
npx skills add https://github.com/agentik-os/OmegaOS --skill planner-agentik-os
Please help me install this Agent Skill. Skill: planner Source: https://github.com/agentik-os/OmegaOS/tree/main/skills/planner Command: npx skills add https://github.com/agentik-os/OmegaOS --skill planner-agentik-os
OmegaOS-native implementation planner reads Vision/PRD/CLAUDE.md, decomposes the work into a DAG of single-worker-dispatch steps, and emits a typed .planner/tracker.json that the Rust engine omega plan-run executes with structural can't-skip enforcement (Gate) and independent verify-command proof (Guardian). Replaces the prose-only VPS planner: sequential execution is enforced by the engine, not by instructions.
Describe Vision/PRD goals and let the planner generate a .planner/tracker.json to drive omega plan-run.
High-intent search queries and answers about installing and using this skill.
To convert goals into a planning DAG, the planner reads Vision/PRD/CLAUDE.md files and decomposes them into single-worker tasks, emitting a typed .planner/tracker.json with phases, dependencies, and touch-file metadata.
Deterministic workflow planning enforces sequential execution by emitting a tracker JSON that the omega plan-run engine orchestrates, applying structural Gate enforcement and independent Guardian verify-command proofs rather than relying on prose instructions.
To generate a tracker JSON for task decomposition, you need existing Vision, PRD, or CLAUDE.md files describing your goals. The planner reads these inputs to produce the ready-to-run .planner/tracker.json file.
Yes, the planner supports multi-language prompts and reusable planning templates. This allows you to decompose goals into verifiable steps aligned with Vision/PRD requirements while maintaining consistent handoffs.
A DAG-based task planner replaces prose-only approaches by shifting sequential execution enforcement from instructions to the execution engine. It provides structural can't-skip enforcement and independent verification proof for every single-worker task.
Yes, the generated .planner/tracker.json drives the omega plan-run engine to orchestrate execution with Gate and Guardian verification. It includes explicit dependencies and file-touch scopes for structural enforcement.
ezagent42Extract modules, user stories, NFRs, constraints, and dependencies from a PRD into YAML.
zhixuan312Dispatch Markdown plan tasks sequentially to a single worker session.
the-omega-instituteApply the Omega Reasoning Protocol to audit derivation chains via forcing, minimization, and audit principles.
agentscope-aiGenerate ordered step-by-step execution plans with dependencies and verification points.
