planner

Convert complex requests into structured, dependency-aware roadmaps with approval pauses.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/MuharremTozan/Ohm-Yura --skill planner-muharremtozan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/MuharremTozan/Ohm-Yura/tree/main/.agents/skills/planner
Command: npx skills add https://github.com/MuharremTozan/Ohm-Yura --skill planner-muharremtozan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a centralized planning authority that converts complex requests into structured, phase-by-phase roadmaps with explicit dependencies and mandatory gap-resolution steps before any plan is saved.

Core Features & Use Cases

  • High-fidelity planning orchestration: Transforms multi-step requests into sequential, dependency-aware roadmaps with embedded validation steps.
  • Pre-planning discipline: Performs Skill Awareness scans and mandatory gap audits to surface questions before planning.
  • Plan governance and approval workflow: Enforces a mandatory pause for approval after drafting the roadmap to prevent unapproved changes.

Quick Start

Describe your project goal and constraints and the planner will generate a structured, phased roadmap after performing a pre-planning scan.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I turn complex software requests into structured roadmaps?

Complex software requests are transformed into structured roadmaps through dependency-aware task sequencing, gap audits, and a mandatory pre-planning scan that enforces sequential phases before final plan approval.

What is dependency-aware task sequencing for multi-step implementation?

Dependency-aware task sequencing organizes multi-step implementation and refactoring tasks into sequential phases, ensuring prerequisite steps are resolved before downstream execution to guarantee full project traceability.

How do I perform gap analysis and task decomposition before planning a software project?

Gap analysis and task decomposition are performed during mandatory pre-planning scans, surfacing unresolved questions and breaking complex requests into structured phases before any roadmap is saved.

Does the roadmap planning process require approval before saving changes?

Yes, the roadmap planning process enforces an explicit pause for approval after drafting the initial phases, preventing any unapproved changes from being saved until the user reviews the generated plan.

Can I use this planning approach for system design and refactoring tasks?

This planning approach applies directly to system design and refactoring tasks, converting complex constraints into phased roadmaps with embedded validation steps to ensure complete architectural coverage.

When should I not use automated roadmap generation for software projects?

Automated roadmap generation should be avoided when a project lacks defined constraints or goals, as the mandatory gap audit and pre-planning discipline will block plan saving until unresolved questions are answered.