planning-agent

Name: planning-agent
Availability: InStock
Author: aseesy

Generates phase-based execution plans for complex user requests.

Updated Aug 27, 2026

Search Tags:#workflow #planning #SDD #plan #specification-driven development

Ready to run

npx skills add https://github.com/aseesy/DEMO --skill planning-agent-aseesy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-agent
Source: https://github.com/aseesy/DEMO/tree/main/.claude/skills/sdd-workflow/planning-agent
Command: npx skills add https://github.com/aseesy/DEMO --skill planning-agent-aseesy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides procedural guidance for the planning workflow, detailing Phase 0 (Research) through Phase 2 (Validation) and ensures alignment with constitutional principles and non-autonomous git operations.

Core Features & Use Cases

Phase guidance: Clear steps for setup, analysis, and execution.
Compliance touchpoints: Checks against constitution principles for plan generation.
Interaction protocol: Guidelines for agent collaboration and handoffs.

Quick Start

Consult the planning-agent for understanding or executing the /plan workflow. Use it as a reference to guide planning tasks.

Frequently Asked Questions about planning-agent

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

FAQPage Schema

How do I structure a multi-phase workflow plan for complex tasks?▼

Multi-phase workflows organize complex requests into sequential stages: Phase 0 (Research) gathers context, Phase 1 (Execution) implements steps with explicit approvals, and Phase 2 (Validation) ensures compliance. This structure transforms unstructured requirements into step-by-step procedures that enforce governance constraints and documentation synchronization.

What is specification-driven development and when should I use it?▼

Specification-driven development (SDD) frontloads planning and requirements definition before execution, reducing ambiguity and rework. Use it for research, design, and validation scenarios where constitutional compliance, explicit approvals for operations like git changes, and comprehensive documentation are mandatory.

How do I ensure git operations are approved before execution in my workflow?▼

The planning workflow mandates explicit approval gates for git operations as a governance constraint. Phase 1 execution requires documented approval before any git action proceeds, preventing autonomous changes and maintaining audit compliance across your workflow phases.

Can I use phase-based planning for design and research workflows?▼

Yes. Phase-based execution plans apply across domains requiring stepwise initialization, processing, and validation—including research, design, and validation scenarios. The framework enforces constitutional principles and comprehensive documentation synchronization regardless of domain.

What documentation must be synchronized during planning execution?▼

Comprehensive documentation synchronization is a core governance mandate throughout all workflow phases. Plans must align internal documentation, requirement specifications, and compliance records to maintain constitutional alignment and enable transparent handoffs between agent collaboration stages.