plan-cookbook-recipe

You create a new agentic cookbook recipe through guided interactive discussion that handles stepwise discovery, category selection, compliance verification, and automated git commits without writing implementation code.

Ensuring cookbook recipe compliance and proper categorization is handled automatically through dev-team linting, inline evaluation, and automatic category discovery with INDEX.md updates during the interactive design process.

Yes, you can use interactive design to extend UI components, infrastructure patterns, or app behaviors within the cookbook repository through stepwise discovery and automated file generation.

Dev-team linting or inline evaluation is used to verify compliance for new cookbook recipes, ensuring repository consistency and proper categorization during the automated generation and git commit process.

Creating a cookbook recipe manually causes repository consistency issues because it is error-prone and time-consuming, particularly when ensuring proper categorization, compliance, and INDEX.md updates are done without automated guidance.

You should not use guided interactive design for cookbook recipes when you need to write actual implementation code, as this process focuses on design, compliance verification, and automated git commits without generating implementation logic.