Audience: techies (devs, tech leads, architects) and involved partners (product, design, quality). This guide excludes external stakeholders and pre/post launch activities — it’s about how a small team learns, plans, and ships together while pairing with agentic AI.
Imagine a small cross-functional team: a couple of engineers, a tech lead (Dahshan), a product owner (Karema), and a designer (AbdulHamid - Abdu). They have an idea. They also have a new comer — an agentic AI we nickname (Shiko) — who can think, suggest code, write drafts, propose test scaffolds, and summarize docs.
This story is about how the team pairs with Shiko to amplify their work — not replace it. Human critical thinking, planning, leadership and process remain the drivers.
From day one we agree on a simple rule: AI helps us having widened vision and multiplied productivity — it must never make decisions alone.
Every product starts as a spark — an idea. But turning that spark into something real, usable, and testable takes structure, discipline, and the right partners. In our case, that partner isn’t just our team, but also the new comer; Shiko.
We slow down to think, map, and question. Here, we sketch blueprints, draft journeys, and define what needs to exist. This is where clarity is built, for us now and for others later.
📽️ Story moment: Karema and Abdu sit together, sketching the product on a whiteboard. They convert the scribbles into feature md files in docs/features — small, focused docs that are easy to read which contains: (Shiko can contribute here)