perfectcode-zen-plan

Coordinates multi-agent planning to produce comprehensive feature plans in .opencode/plans.

11|2|Updated Feb 18, 2026

Search Tags:#planning #architecture #requirements #multi-agent #governance #feature-planning

Ready to run

npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill perfectcode-zen-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: perfectcode-zen-plan
Source: https://github.com/the-perfect-developer/the-perfect-opencode/tree/main/.opencode/skills/perfectcode-zen-plan
Command: npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill perfectcode-zen-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, multi-agent planning workflow that routes feature requests through clarification, parallel blueprint production, and senior arbitration when needed, ensuring a thorough plan is produced and stored in .opencode/plans before any building begins.

Core Features & Use Cases

Parallel Tier 1 blueprints produced by @code-analyst, @performance-engineer, @devops-engineer, @test-engineer, and @explore in parallel.
Tier 2 arbitration by senior consultants (@principal-architect, @solution-architect, @database-architect, @security-expert) when conflicts or high-stakes decisions arise.
The final plan documents cover summary, scope, architecture, implementation tasks, testing strategy, migration path, rollout plan, and open questions.

Quick Start

Provide a kebab-case feature name and initial requirements, then trigger the Zen planning workflow to generate a complete plan saved to .opencode/plans/<feature-name>.md.

Frequently Asked Questions about perfectcode-zen-plan

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

FAQPage Schema

How do I create a comprehensive feature plan before implementation begins?▼

Multi-agent feature planning uses parallel blueprints from code, performance, devops, and test engineers, followed by senior architect arbitration to resolve conflicts and produce a final structured plan stored in .opencode/plans.

What is multi-agent planning and how does it resolve architectural conflicts?▼

Multi-agent planning assigns parallel blueprint generation to specialized engineering agents, then escalates high-stakes conflicts or design decisions to senior architect and security agents for arbitration before producing the final plan.

What sections should a complete feature rollout and migration plan include?▼

A complete feature plan should include sections for summary, scope, architecture, implementation tasks, testing strategy, migration path, rollout plan, and open questions to guide downstream development work.

How do I start the planning workflow with a new feature request?▼

To start the planning workflow, provide a kebab-case feature name and initial requirements, then trigger the workflow to automatically generate a complete plan saved to .opencode/plans/<feature-name>.md.

When should I use senior architects for arbitration in feature planning?▼

Senior architect arbitration should be used during feature planning when conflicts arise between parallel engineering blueprints or when high-stakes architectural, database, or security decisions need resolution.

Does multi-agent feature planning work without external dependencies?▼

Multi-agent feature planning operates without external dependencies, coordinating internal agents for blueprint production and arbitration to generate comprehensive plans independently.