Autonomy action mein: Jira ticket se PR tak
Ahem marhala. Claude Code do real tickets ko description se merged code tak le jata hai — pehle dataset curate karta hai, phir polished Next.js NDA app banata hai — aur raaste mein aane wali rukawaton ko khud solve karta hai.
Har cheez connect ho chuki hai: Jira input ke liye, GitHub output ke liye, aur darmiyan mein rails par FeatureDev. Ab hum isay unleash karte hain. Is page par Claude Code do real tickets ko description se merged code tak le jata hai, taqreeban baghair kisi madakhalat ke — aur, itna hi qeemti yeh dekhna hai ke jab woh kisi rukawat se takrata hai to khud rasta nikal kar problem solve karta hai. Yeh woh lamha hai jiski taraf poora hafta barh raha tha.
01Aik aham ticket: dataset curate karna (PL-2)
Hamara pehla serious task aik data-curation job hai. Pre-Legal ko kaam karne ke liye document templates ki library chahiye. Iske liye aik behtareen muft source hai: Common Paper, jo standard legal agreements (mutual NDA waghera) ko Markdown mein publish karti hai — jo LLMs ko bohot pasand hai — aik aasan Creative Commons licence ke tehat. Jira mein hum PL-2 banate hain aur usay aik wazeh, human-level description dete hain:
“Create a dataset of legal document templates the system can later modify for the user. Browse the
Common Paper GitHub repos, pull down the Markdown files into a templates directory, add a
catalog.json describing each template, and include a licence file recognising the CC
licence.”
Style note karein: high-level aur insani andaz, jaisa koi product owner likhta hai. Yeh kaise karna hai ka faisla Claude par chhorta hai.
02Per-project setup & re-auth ritual
Aik ahem baat: MCP servers har project ke liye alag register ho sakte hain. Agar aapne Atlassian kisi aur folder mein install kiya tha,
to yahan dobara add karein, phir /mcp → Re-authenticate karein (har bare task se pehle yeh
karna hoga — Approve, Accept, done). Ab seedha plain-English prompt:
Please carry out Jira issue PL-2 and raise a PR with your changes.
03Real time mein problem solve karte dekhein
Kaam shuru hota hai: Claude PL-2 fetch karta hai, zaroorat samajhta hai, aur GitHub tool ke sath files pull karna shuru karta hai. Phir aik dilchasp cheez hoti hai.
Claude samajh jata hai ke iska pehla tareeqa — lambi files ko aik aik karke context mein lana — bohot slow aur wasteful hai. Is liye woh rukta hai, dobara sochta hai, aur aik behtar tareeqe par switch karta hai: files ko direct download karne ke liye commands run karta hai. Usay rukawat mili, samajh aayi ke kyun mili, aur uske gird aik behtar rasta banaya — aisi samajh boojh pehle ke models mein mumkin nahi thi.
Nateeja: Markdown agreements se bhara templates/ directory, unki wazahat karta
catalog.json, aur aik license.txt — bilkul wohi jo ticket ne manga tha. Usne pehle GitHub command-line tool chalane ki koshish ki, dekha ke install nahi hai, to PR open karne ke liye apne MCP tool par fallback kiya. Adaptive, pur-azm, autonomous.
Jab Claude ne Jira mein PL-2 ko done mark karne ki koshish ki, to woh hang ho gaya — auth dobara expire ho gayi thi.
Solution ab yaad ho chuka hai: Esc, /mcp, Re-authenticate, phir
“please try marking the Jira issue complete again.” Pur-sakoon retry hi taqreeban hamesha mukammal ilaj hota hai.
04Bina merge rights ke bhi merge karna
PL-2 ke done hone ke baad, hum Claude se PR merge karne aur main par switch karne ko kehte hain. Dilchasp
twist: hamare fine-grained token mein merge permission nahi hai. Himmat haarne ke bajaye, Claude locally merge karke main par push
kar deta hai — aik hi maqsad tak pohnchne ka doosra rasta. Dobara: woh masle ke peeche wajah ko samajhta hai aur munasib hal nikalta hai.
05Asal feature: Next.js NDA app (PL-3)
Ab asal build ki baari hai. Jira mein hum PL-3 banate hain, customer ke andaz mein — jaan boojh kar thora flexible, taake Claude ke paas achhe faislay lene ki jagah ho:
“A web application to create a mutual NDA document for a user. The user enters key information in a form; the website displays the mutual NDA with that information filled in; the user can download the completed document locally.”
Is dafa hum plugin ko directly invoke karte hain — “use FeatureDev” kehne ki zaroorat nahi:
feature-dev:feature-dev Please implement Jira issue PL-3 with a Next.js application in a directory called frontend and raise a PR when done.
Aik hi line sab kuch jor deti hai: ticket ke liye Jira (MCP), process ke liye FeatureDev (plugin), PR ke liye GitHub (MCP). Apne usoolon ke mutabiq, FeatureDev clarify stage par rukta hai aur samajhdaranah sawalat poochta hai — bilkul unhi khalaon ko pur karta hai jo humne chhore the:
| Yeh poochta hai… | Hum chunte hain |
|---|---|
| NDA kis format mein download ho? | PDF (iski apni recommendation) |
| Single-step wizard ya single-page form? | Single page |
| Preview kaise show ho? | Form ke sath Side by side |
| Simple prototype ya styling polish? | Styling polish |
Phir yeh build karta hai — Next.js app scaffold karta hai, components likhta hai, aur PR open karta hai. Isay
cd frontend && npm run dev se chalayein aur dekhein: aik behtareen mutual-NDA creator. Form
fill karein aur live preview type karte waqt live update hota hai; Download PDF click karein aur cover sheet aur CC attribution ke sath clean, correctly-filled document tayyar. Ticket se zero-shot build.
06“Aapne asal mein kya test kiya?”
Kaam kar raha hai — lekin kya isne har stage follow ki? Hum seedha poochte hain: “Based on the process you followed, what quality review or testing have you done?” Imandaranah jawab: isne quality-review stage skip kar di thi — koi automated tests nahi, koi code-review agents nahi, sirf build check. Sirf hamare poochne par hi maloom hua ke stage miss hui.
Hum kehte hain: “Yes to all three — add extensive automated and manual tests, and have the code-reviewer agents review.” Yeh ~10 minute kaam karta hai, test suite sahit 8,000+ lines likhta hai, apne context ke auto-compact hone ke bawajood sambhalta hai, aur 5 suites mein 76 passing tests deliver karta hai. Phir hum aakhri baar re-authenticate karke PR merge karwate hain, main par push karte hain, aur PL-3 ko done mark karte hain.
Autonomy ka matlab “chhor kar chale jana” nahi hai. Iska matlab yeh hai ke Claude mushkil kaam kare jabke aap har stage par guide karein, sawal karein, aur verify karein. Aapke behtareen sawalat (“aapne kya test kiya?”) un khalaon ko pakadte hain jo staged process bhi chhor sakta hai.
✓ Aham baatein
- Tickets human, high level par likhein; kaise karna hai ka faisla Claude par chhorein.
- Claude kaam ke doran problem-solve kar sakta hai — slow tareeqe se behtar tareeqe par switch karna, ya missing merge rights ke waqt locally merge karna.
- Plugin ko seedha
feature-dev:feature-dev …se invoke karein — aik line Jira, build process, aur GitHub PR ko jor deti hai. - FeatureDev wazahat ke sawalat poochne ke liye rukta hai; aapke jawabat build ko shape dete hain.
- Har stage verify karein: yeh quality review skip kar sakta hai aur sirf poochne par batata hai — phir thori si hidayat par 76 tests ka suite tayyar ho jata hai.