recipe-testing

What problem does it solve?

This skill streamlines the creation of ultra-simple test-stage recipes and defers canonical publishing until user approval, reducing upfront effort while preserving quality control.

Core Features & Use Cases

• Collect minimal inputs (dish name, 3-8 ingredients, serving size, rough prep time, cook time, and optional flavor notes) to draft a simple recipe.
• Generate a concise, 3-6 step workflow using metric units and avoiding complex techniques.
• Enforce an explicit approval flow: summarize the recipe and wait for "approved" before adding to the testing list.
• Tag approved recipes with "testing" and a non-canonical note when added to the app.

Quick Start

Provide the dish name, main ingredients (3-8 items), serving size, rough prep time and cook time, and any must-have flavor notes (optional). The system will draft a brutally simple recipe (3-6 steps) using metric units and present a clear confirmation prompt: reply "approved" to add to the testing list. If not approved, revise inputs and repeat. On approval, the recipe is added to the testing list with the "testing" tag and a note indicating it is a non-canonical test entry.