V1 ki planning: Jira tickets likhna
Product ko bilkul real team ki tarah plan karein — PL-4 se PL-7 tak wazeh tickets ka backlog, jo stakeholder ki aawaz mein likha gaya ho, aur phir aik aik karke apne sab se qabil teammate ko sonpa gaya ho: Claude Code.
Buniad rakh di gayi hai. Ab hum asal product ko real team ki tarah plan karte hain — tickets likh kar. Tasawwur karein ke aapka engineering lead, product manager, business sponsor, ya clients bhi Jira mein yeh daal rahe hain. Aam taur par yeh poori team mein taqseem hotay hain; hum yeh sab aik intehai qabil teammate ko assign karne ja rahe hain: Claude Code.
01Prototype se real V1 tak
Jira mein wapis ja kar safai karein: chhota sa “simple website” card (PL-1) apna maqsad poora kar chuka hai, lehaza usay delete kar dein. NDA prototype (PL-3) ne concept sabit kar diya. Ab hum mukammal V1 ke safar ko chand wazeh tickets mein taqseem karte hain, har ticket aik meaningful step hai jise stakeholder pehchan sake.
02Chaar V1 tickets
Yeh raha plan — jaan boojh kar business aur technical aawazon ke imtizaj ke sath likha gaya hai, kyunki real life mein yeh mukhtalif logon ki taraf se aatay hain:
| Ticket | Title | Yeh kya mangta hai |
|---|---|---|
| PL-4 | Build foundation of V1 | Prototype ko aik proper technical foundation mein upgrade karein — frontend, backend aur temporary database start/stop scripts ke sath — abhi naye product features add kiye baghair. (Technical-lead ka ticket.) |
| PL-5 | Add AI chat (still just NDA) | Product ke interact karne ka tareeqa tabdeel karein: sawalat ki series ke bajaye, AI ke sath free-form chat jo document ke baare mein poochhe, fields ke baare mein poochhe, aur jawabat se usay populate kare. |
| PL-6 | All document types | Har us document ko support karne ke liye expand karein jiske hamare paas templates hain. Agar user koi unsupported document chahta hai, to explain karein ke hum yeh generate nahi kar sakte — lekin qareebi tareen mutabadil offer karein. |
| PL-7 | Multiple users & final polish | Proper sign-up / sign-in; pehle se generate kiye gaye documents ko store aur re-open karna; database restart par reset ho sakta hai; har screen ko professional SaaS jaisa polish karein; aur “draft, subject to legal review” disclaimer add karein. |
Ghaur karein ke PL-5 mein Cerebras ya structured outputs ke baare mein kuch nahi kaha gaya — yeh jaan boojh kar kiya gaya hai. Tickets kya karna hai (what) ko insani alfaaz mein bayan karte hain; kaise karna hai (how) CLAUDE.md, skill, aur Claude ke apne faislay se aata hai. Gunjaish chhorna aik feature hai, laparwahi nahi.
03Fake login se shuru karein
PL-4 ke liye hum aik baat par wazeh hain: abhi sirf fake login screen, koi real authentication nahi — bas user ko platform ke andar le aana hai. Hum shuru mein hi auth nahi thopna chahte; real sign-up/sign-in PL-7 mein aayega. Mushkil hisson ko baad ke liye schedule karna har ticket ko chhota aur shippable rakhta hai.
04Product owner ki tarah sochein
✅ Description mein detail daalein
Requirement ko ticket ke Description field mein likhein — kyunki Claude wohi padhta hai. (Ghalti se Comments box mein type kar dena intehai aasan hai!)
✅ Business-speak bilkul theek hai
“Product ke user ke sath interact karne ka tareeqa badlein” aik behtareen ticket hai. Aapko code ki zuban mein bolne ki zaroorat nahi — yeh model ka kaam hai.
Board par PL-4 se PL-7 ke sath, hamara Kanban aik real product backlog jaisa lagta hai. Kisi company mein yeh mukhtalif engineers ko milte. Hum yeh saara kaam aik aik karke Claude Code ko sonpne ja rahe hain.
05Claude ko assign karein — aur check karein ke skill load ho gayi
Terminal mein claude chalayein aur /context run karein. Build karne se pehle do cheezein confirm karein:
Aapki skill recognise ho gayi haicheck
Aapko Cerebras inference aik project skill ke tor par listed nazar aani chahiye — jo is baat ka sabot hai ke .claude/skills/cerebras folder theek se connect ho chuka hai.
Plugins & MCP servers mojood haincheck
FeatureDev, aur aapke Atlassian aur GitHub MCP tools. Note karein ke yeh context ka aik munasib hissa use karte hain — yeh MCP trade-off ka amli saboot hai.
Atlassian ko re-authenticate kareinritual
Aap tareeqa jante hain: /mcp → Atlassian → Re-authenticate → Approve → Accept. Isay skip karenge to pehla Jira read hang ho jayega.
✓ Aham baatein
- V1 ko chand wazeh tickets (PL-4 se PL-7) ke tor par plan karein, har ticket aik aisa step ho jise stakeholder pehchan sake.
- Tickets ko insani/business zuban mein likhein; kaise karna hai CLAUDE.md, skill aur Claude ke faislay par chhor dein.
- Mushkil hisson ko schedule karein: pehle fake login (PL-4), real auth baad mein (PL-7).
- Requirements ko Description field mein daalein, Comments mein nahi — kyunki Claude Description padhta hai.
- Build karne se pehle confirm karein ke aapki project skill
/contextmein show ho rahi hai, aur Atlassian ko re-authenticate karein.