planning-hub

Orchestrate seven-phase project planning with checkpointed sub-agent dispatch and validated plan artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gleeb/ai-registry --skill planning-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-hub
Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/planning-hub
Command: npx skills add https://github.com/gleeb/ai-registry --skill planning-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning across multiple agent roles is hard to coordinate consistently, especially when plans evolve over time; this hub centralizes a repeatable planning workflow and keeps per-story artifacts as the source of truth.

Core Features & Use Cases

  • 7-phase planning orchestration per project: runs PRD, system architecture, story decomposition, per-story HLD/API/Data/Security/Design planning, then cross-cutting rollups and final execution readiness.
  • Dispatches specialized sub-agents with strict boundaries: uses deterministic phase and dispatch targets to ensure each agent produces the correct plan artifacts without mixing responsibilities.
  • Validation and checkpoint-driven progress control: integrates checkpointing before and after dispatches, supports resume, logs dispatch/response events, and gates progression on validator passes.
  • Brownfield change impact analysis: classifies change level and re-dispatches only the minimum required agents after impact analysis.
  • Optional external SaaS synchronization: can translate internal plan artifacts to external systems if configured, without making SaaS mandatory.

Quick Start

Start a new planning session by running the planning hub with your initial user request, and let it drive PRD, architecture, story decomposition, and per-story planning while writing all outputs into the internal plan/ folder structure.

Frequently Asked Questions about planning-hub

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

FAQPage Schema
How do I orchestrate multi-agent project planning across PRD, architecture, and story decomposition phases?

Multi-agent project planning orchestration is driven by a 7-phase workflow covering PRD, system architecture, story decomposition, and per-story HLD/API/Data/Security planning. It uses deterministic phase and dispatch targets to route sub-agents and writes validated plan artifacts into a structured plan folder.

What is the best way to handle brownfield re-planning and change impact analysis for evolving requirements?

Brownfield re-planning handles evolving requirements by classifying the change level through impact analysis and re-dispatching only the minimum required sub-agents. This ensures updated plan artifacts remain consistent and traceable through validators without re-running the entire workflow.

How does checkpoint validation work for per-story plan artifacts in an automated planning workflow?

Checkpoint validation for per-story plan artifacts works by integrating checkpointing before and after sub-agent dispatches. Progression is gated strictly on validator passes, with support for resume and event logging to maintain artifact consistency as the single source of truth.

Can I use planning hub for incremental feature additions without re-planning the entire system architecture?

Yes, planning hub applies to incremental feature additions alongside greenfield planning and brownfield re-planning. It isolates impact analysis to the specific change level and re-dispatches only the necessary agents, preventing full system architecture re-planning.

Do I need external SaaS synchronization to maintain project plan artifacts?

No, external SaaS synchronization is entirely optional. The workflow maintains internal plan artifacts as the single source of truth by default, and can optionally translate these outputs to external systems if configured without making SaaS mandatory.