planner

Plan and execute multi-team projects with integrated quality review gates.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/marqus0004/LifeIsRoadBlocks --skill planner-marqus0004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/marqus0004/LifeIsRoadBlocks/tree/main/skills/planner
Command: npx skills add https://github.com/marqus0004/LifeIsRoadBlocks --skill planner-marqus0004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Complex tasks stall when requirements are not captured, teams lack alignment, and quality gates are absent. Planner provides a structured planning and execution workflow with built-in gates to ensure decisions, plans, and documentation are aligned before coding.

Core Features & Use Cases

  • End-to-end planning and execution for multi-step projects requiring cross-team collaboration
  • Integrated quality review gates (QR) to catch design defects, ensure traceability, and enable safe iteration
  • Centralized state management (plan.json, context.json, qr-*.json) with automated documentation workflows to keep artifacts synchronized

Quick Start

Describe your task and I will automatically start the planning workflow.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I prevent requirements drift in multi-team software architecture projects?

Quality review (QR) gates are integrated verification checkpoints within the planning workflow that catch design defects, ensure traceability, and enable safe iteration by validating requirements before and during coding phases.

How do I plan and execute complex tasks with automated documentation alignment?

Yes, you can manage architecture decisions and documentation alignment by applying per-phase quality review verification and centralized state mutations to keep plans and artifacts synchronized across coding workflows.

When do I need quality gates for project planning and orchestration?

Yes, you can manage architecture decisions and documentation alignment by applying per-phase quality review verification and centralized state mutations to keep plans and artifacts synchronized across coding workflows.

What is the best way to audit complex task execution across planning and coding workflows?

You need quality gates for project planning and orchestration when managing multi-step cross-team tasks that require iterative verification, architecture decisions, and documentation alignment to prevent stalling before coding begins.

Does this planning workflow support diagram rendering and artifact synchronization?

The best way to audit complex task execution across planning and coding workflows is to implement centralized state management with automated artifact synchronization and per-phase quality review verification to ensure end-to-end traceability.