meow:cook

Orchestrate end-to-end feature implementation with a seven-phase MeowKit workflow and TDD gating.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables end-to-end feature implementation by enforcing a seven-phase MeowKit workflow with strict TDD gating, ensuring every feature is planned, tested, and reviewed before deployment.

Core Features & Use Cases

  • End-to-end pipeline: coordinates phases from Orient to Reflect with built-in memory capture and review gates.
  • TDD-enforced workflow: requires writing failing tests before implementation and validating via Gate 1 and Gate 2 checks.
  • Plan-driven execution: uses plan files and subagents to research, build, review, and ship features in a controlled, auditable manner.
  • Use Case: teams delivering complex features can iteratively plan, test, implement, review, and document changes across multiple teams.

Quick Start

Provide a plan and tests before implementing features using the cook skill.

Frequently Asked Questions about meow:cook

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

FAQPage Schema
How do I enforce test-driven development before implementing new features?

To enforce test-driven development (TDD) before feature implementation, use a workflow that requires writing failing tests first. A TDD-enforced workflow uses validation scripts to act as phase gates, ensuring no code is built without prior test creation and approval.

What is a plan-driven end-to-end feature delivery workflow?

A plan-driven end-to-end feature delivery workflow orchestrates the entire implementation lifecycle from orient to reflect. It coordinates subagents for scouting, planning, testing, building, reviewing, shipping, and memory capture, ensuring every phase is executed in a controlled and auditable manner.

How do I add phase gates to validate feature planning and testing?

You add phase gates by integrating validation scripts like validate-gate-1.sh and validate-gate-2.sh into your workflow. These gating scripts check that planning and testing prerequisites are met before allowing the feature implementation pipeline to proceed to the building phase.

Can I run TDD workflows in parallel or without tests for quick prototypes?

Yes, you can run TDD workflows in parallel or without tests by configuring specific execution modes. The workflow supports code, parallel, auto, and no-test modes, allowing teams to adapt the strict phase gating and subagent coordination based on project complexity and speed requirements.

Does this feature implementation workflow support memory capture for future iterations?

Yes, the feature implementation workflow supports built-in memory capture during the reflect phase. By integrating memory capture directly into the delivery pipeline, it ensures that code review outcomes, planning decisions, and testing insights are documented for future development iterations.

What is the best way to coordinate subagents for complex feature delivery?

The best way to coordinate subagents for complex feature delivery is using a structured seven-phase workflow. This approach assigns specific roles like scouting, building, and reviewing to subagents, enforcing strict TDD governance and phase gates to maintain an auditable, plan-driven execution.