Autonomous workflow aur master cheat-sheet
Aapki revision ka finale. Hum poore professional loop ko dobara dekhenge — ticket se merged pull request tak — phir aik cheat-sheet aur chhota self-check denge taake week three mein aap poore bharose ke sath qadam rakhein.
Weeks one aur two ka urooj aik real product tha jo professional tareeqe se bana. Ab yaqeen kar lein ke is workflow ki shakal aapko doosri fitrat ki tarah yaad hai — kyunki week three iske bade hisson ko automate karega.
01End-to-end loop
Professional workflow aik aisa loop hai jo kaam ke aik unit se shuru hota hai aur reviewed, merged code par khatam — har qadam tracked hota hai.
02FeatureDev ki discipline
Agent ko akela chhor dein to woh code ki taraf bhaagta hai. FeatureDev (Anthropic ka plugin) aik disciplined, stages wala process lazmi banata hai — explore karein, plan banayein, aur code likhne se pehle sign-off lein, phir build aur verify karein. Yeh trust-but-verify mindset ko repeatable process mein badal deta hai.
Jab aap kai agents ko aik waqt mein kaam dete hain, to shared plan hi unhein aik doosre se takrane se rokta hai. FeatureDev ki “pehle plan par muttahid ho jao” wali aadat plan.md ban jati hai jo Class 12.2 mein poori agent team ko coordinate karti hai.
03Hum ne asal mein kya ship kiya
Pre-Legal SaaS ne har dhage ko aik real product mein jor diya:
Tickets + custom skill
Stakeholder ki zaban mein PL-4–PL-7 ka backlog, aur fast, structured LLM calls ke liye aapki apni Cerebras skill.
Kaam karta platform
Multi-user auth, saved documents, aur legal templates bharne wali AI chat — FastAPI + Next.js + SQLite, reviewed PRs ki surat mein ship kiya gaya.
Apni review ke baad bhi Claude ne specified legal disclaimer chhor diya. Ticket ke muqable mein verify karein — agent ka confidence proof nahi hota. Yehi aadat swarm ko imaandaar rakhti hai.
04Master cheat-sheet
| Jab aap chahen… | Yeh use karein |
|---|---|
| Context window dekhein ya wapas hasil karein | /context, phir /compact ya /clear |
| Agent ko mustaqil hidayaat dein | Aik lean CLAUDE.md |
| External system connect karein | MCP server (Jira, GitHub, docs) |
| Repeatable skill sikhayein | .claude/skills/ mein aik skill |
| Apna type kiya hua shortcut add karein | Aik slash command (Class 12.3) |
| Shor wala task alag dein, context bachayein | Aik sub-agent (Class 12.4) |
| Kisi event par kuch automatically karayein | Aik hook (Class 12.5) |
| Poora setup bundle aur share karein | Aik plugin + marketplace (Class 12.6) |
| Ghanton tak hands-off build karein | Aik Ralph loop / swarm (Git ke zariye!) |
| Ghalat qadam undo karein | Rewind / aik clean Git commit |
05Jaldi se self-check
In sawalon ke jawab buland awaaz se dein. Agar koi jawab dhundla ho to linked page aapka revision target hai.
CLAUDE.md use na karein to agent “bhoolta” kyun hai?
Hint: har turn par transcript ke sath kya hota hai? (11.2 dekhein)
MCP vs. skill vs. plugin — har aik ki aik line.
Connect / teach / bundle. (11.3 dekhein)
Control↔autonomy dial par “trust but verify” kahan hai?
Centre ke baen taraf — aur kyun? (11.1 dekhein)
YOLO mode ke neeche safety net kya hai?
Agar foran jawab na de sakein to finale se pehle 11.3 revise karein.
Agar in chaaron ke jawab aasani se aa gaye to weeks 1–2 poore aapke zehan mein hain. Ab bara sochne ka waqt hai: Class 12 finale ke mindset — controlled chaos — ke sath shuru hoti hai.
✓ Ahm baatein
- Pro loop: ticket → FeatureDev (plan/build/test) → reviewed PR → repeat.
- Staging (“pehle plan par muttahid ho jao”) shared
plan.mdban jati hai jo kai agents ko coordinate karti hai. - Hum ne real multi-user SaaS ship kiya — aur phir bhi ticket ke muqable mein verify karna pada.
- Cheat-sheet paas rakhein: yeh har “main yeh karna chahta hoon…” ko sahi tool se milati hai.
- Self-check pass karein, phir Class 12 mein controlled chaos ki taraf qadam rakhein.