meow:plan-creator

Draft gate-driven planning documents with YAML frontmatter and acceptance criteria for MeowKit implementations.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-plan-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meow:plan-creator
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Aplan-creator
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-plan-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Planning complex MeowKit tasks often requires structured, gate-driven documents with standardized frontmatter and sections. This Skill automates plan creation, validates completeness, and coordinates Gate 1 approvals to reduce fragmentation and rework.

Core Features & Use Cases

  • Structured plan templates: pulls from assets/plan-template.md to shape plan.md with required sections.
  • Gate-1 readiness: validates plan completeness before proceeding and generates a Context Reminder for execution.
  • Lifecycle guidance: references workflow models, plan organization, and task management guidelines to support cross-session handoffs.

Quick Start

Create a planning plan.md from the template and run the validator to ensure PLAN_COMPLETE.

Frequently Asked Questions about meow:plan-creator

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

FAQPage Schema
How do I create a structured planning document with mandatory YAML frontmatter and acceptance criteria?▼

To create a structured planning document, use plan templates that enforce mandatory YAML frontmatter, required sections, and binary acceptance criteria to define task scope and constraints.

What is gate-driven planning and how does it validate plan completeness?▼

Gate-driven planning validates plan completeness by checking required sections and constraints before proceeding, generating a Context Reminder for execution and coordinating Gate 1 approvals to reduce rework.

How do I track agent state and manage cross-session handoffs for workflow planning?▼

Track agent state and manage cross-session handoffs by referencing workflow models and task management guidelines that support lifecycle guidance throughout the planning process.

Does the plan validator check for binary acceptance criteria before Gate 1 approval?▼

Yes, the plan validator checks for binary acceptance criteria and required sections before proceeding, ensuring PLAN_COMPLETE status is achieved for Gate 1 approval readiness.

What's the best way to automate plan creation for complex implementations?▼

Automate plan creation for complex implementations by pulling from plan templates to shape plan.md, validating completeness, and generating Context Reminders to coordinate Gate 1 approvals and reduce fragmentation.

When do I need a gate-driven plan template for workflow automation?▼

You need a gate-driven plan template for workflow automation when planning complex tasks requires standardized frontmatter, structured sections, and validation to reduce fragmentation and rework.