Sabbir Amin
Someone asked, half joking, "should we just search for a skill.md file for the recipes? Some of us are bachelors." So this is what we've built one over the ( before the) weekend. 🤌
A while back I shared how we adapted agentic software development at TechCare, and two files anchored everything: project.md as the blueprint, tasks.md as the kanban board for agents.
We used the same pattern here, just for cooking. 🍳
📄 project.md had the domain, architecture decisions, DOs, DONTs, naming conventions, and definition of done for every recipe.
✅ tasks.md had the phases, priorities, dependencies, and acceptance criteria. Every session started by binding to both. Cursor worked through the tasks in order without drifting.
For thinking and architecture decisions, we used Claude. 🧠 For the repetitive generation work, six recipes with consistent structure, metric quantities, and step-by-step instructions, we used Kimi K2.5. Fast, cheap, and it followed the schema cleanly. ⚡
The hero image was one prompt to ChatGPT. Done in two minutes. 🎨
Is this a serious project? Not really. But the bachelors in the office can now load a skill and get walked through Chingri Malaikari step by step. 🦐 And we learned that the project.md + tasks.md pattern holds up even for something this small and silly. That is the actual takeaway.
Repo is open if anyone wants to add a recipe or borrow the pattern for something more serious. github.com/sabbiramin113008/agentic-cooking-skill