planning

Generate mermaid diagram-first implementation plans with function signatures and data flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software work often lacks a single, unambiguous artifact that captures entities, data flows, function contracts, parallelization, and dependencies; this Skill produces diagram-first plans that make implementation-ready decisions explicit and reviewable before any coding begins.

Core Features & Use Cases

  • Diagram-first methodology: Produces mermaid-based diagrams that serve as the canonical plan, with function signatures, labeled edges, subgraphs, and parallel markers.
  • Context-driven planning phases: Guides clarifying questions, codebase research, diagram generation, and iterative review to ensure plans are grounded in real project context.
  • Multi-agent orchestration guidance: Advises when to use multi-agent workflows for cross-cutting features (UI, API, DB, external services) and how specialist planners should align on diagram standards and handoffs.
  • Governance rules: Enforces mandatory use of a rendering tool, explicit pause for user feedback, and strict prohibition on starting implementation within the planning phase.

Quick Start

Ask the agent to create a mermaid-based implementation plan for a specified feature, including entities, function signatures, labeled data flows, external dependencies, and a summary of open questions.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a mermaid diagram implementation plan for a software feature?

To create a mermaid diagram implementation plan, you define software entities, function signatures, labeled data flows, and external dependencies. The plan uses subgraphs and parallel markers to make architectural decisions explicit and reviewable before coding begins.

What is diagram-first planning for software architecture changes?

Diagram-first planning uses mermaid diagrams as the canonical artifact to capture entities, data flows, and function contracts. It ensures implementation-ready decisions are explicit, structured, and reviewed before any development starts.

How do I break down complex software tasks into implementable steps across UI and API layers?

You break down complex tasks by analyzing structured entities and applying multi-agent orchestration to cross-cutting features. Specialist planners align on diagram standards and handoffs across UI, API, database, and external services.

Does the planning process allow starting implementation before finalizing the diagram?

No, the planning process strictly prohibits starting implementation within the planning phase. It enforces an explicit pause for user feedback after generating mermaid diagrams to ensure the architectural plan is fully reviewed.

When do I need to use a multi-agent workflow for feature planning?

You need a multi-agent workflow for feature planning when dealing with cross-cutting features that span UI, API, database, and external services. This approach allows specialist planners to align on diagram standards and manage handoffs.

What should be included in a mermaid architecture diagram for codebase research?

A mermaid architecture diagram for codebase research should include function signatures, labeled edges for data flows, subgraphs for system boundaries, and parallel markers. It must be generated using a rendering tool after clarifying questions are answered.