cook

Convert approved specifications into tested code changes with TDD discipline.

15|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/paulnsorensen/easy-cheese --skill cook-paulnsorensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cook
Source: https://github.com/paulnsorensen/easy-cheese/tree/main/skills/cook
Command: npx skills add https://github.com/paulnsorensen/easy-cheese --skill cook-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns an approved spec or an unambiguous implementation request into working code using a disciplined cut → implement → taste-test → handoff loop, so changes are verifiable and review-ready.

Core Features & Use Cases

  • TDD-first implementation loop: writes failing tests before production changes, then makes them pass.
  • Spec/slug-driven workflows: resolves durable spec slugs and reads pasted requirements when provided.
  • Autonomous chaining: uses --auto to flow through /press → /age → /cure with caps and quality gates.

Quick Start

Ask it to implement your requested change by providing the spec or a clear task with acceptance criteria, for example: /cook /cheese/specs/tail-trailing-newline.md

Frequently Asked Questions about cook

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

FAQPage Schema
How do I implement code changes from a spec using TDD?

To implement code changes with TDD, this Skill converts approved specifications into a disciplined cut, implement, taste-test, and handoff loop, writing failing tests first before making minimal production changes to satisfy them.

Can I use autonomous mode for continuous feature implementation?

Yes, you can use autonomous mode for continuous feature implementation by applying the --auto flag to flow through chained stages with built-in caps and quality gates for verifiable, review-ready code.

What is a spec slug and how does it drive code generation?

A spec slug is a durable reference identifier that drives code generation by resolving approved specifications, allowing the implementation loop to read requirements and track the task through to a package-ready report.

Does this TDD implementation approach work for single-file bug fixes?

Yes, this TDD implementation approach works for bounded engineering tasks like single-file bug fixes, small call-site modifications, and feature implementations, provided there is an approved contract or unambiguous request.

What happens during the taste-test phase of the implementation loop?

During the taste-test phase of the implementation loop, code changes are verified with a two-round corrective cap to ensure quality gates are met before producing a package-ready report and a handoff slug.

How do I propagate flags like --open-pr downstream during implementation?

To propagate flags like --open-pr downstream during implementation, the Skill automatically passes --auto, --hard, and --open-pr flags through the autonomous chaining workflow to the final handoff.