https://blog.abhipraya.dev/tags/linear/Recent content in Linear on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaMon, 23 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s2w1-ai-literacy/Mon, 23 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s2w1-ai-literacy/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>This week I used Claude Code (Anthropic&rsquo;s CLI agent) as my primary development partner for Sprint 2 planning, feature brainstorming, code implementation, and CI debugging. The session produced 20 PBIs, 64 subtasks, 3 service file changes, and a merged MR, all in one sitting.</p> <h2 id="ai-for-sprint-planning"> <a class="anchor" href="#ai-for-sprint-planning" data-anchor="ai-for-sprint-planning" aria-hidden="true">#</a> AI for Sprint Planning </h2> <h3 id="feature-gap-analysis"> <a class="anchor" href="#feature-gap-analysis" data-anchor="feature-gap-analysis" aria-hidden="true">#</a> Feature Gap Analysis </h3> <p>I asked Claude to explore the entire codebase (frontend + backend + infra) and catalog what&rsquo;s implemented vs missing. It launched parallel exploration agents that traced through routes, services, workers, and the database schema, producing a comprehensive feature inventory.</p>https://blog.abhipraya.dev/ppl/part-b/s2w1-discipline/Mon, 23 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s2w1-discipline/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>As Team Lead, this week&rsquo;s primary work was Sprint 2 planning. I conducted a full feature gap analysis of the app, brainstormed new features with stakeholder input, created detailed tickets in Linear, set up cross-PBI dependency chains, and rebalanced the sprint when it became overloaded.</p> <p>The result: <strong>20 new PBIs with 64 subtasks</strong>, all with acceptance criteria, technical notes, and proper sprint/cycle assignments.</p>https://blog.abhipraya.dev/ppl/part-b/s2w1-code-review/Mon, 23 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s2w1-code-review/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>This week&rsquo;s review work had two dimensions: reviewing the <strong>ticket board</strong> for sync issues (a form of &ldquo;code review&rdquo; for project management), and letting <strong>SonarQube quality gates</strong> act as automated code review for the monitoring MR.</p> <h2 id="ticket-board-audit"> <a class="anchor" href="#ticket-board-audit" data-anchor="ticket-board-audit" aria-hidden="true">#</a> Ticket Board Audit </h2> <p>After creating 64 new tickets, I audited all 150+ active tickets (Backlog, Todo, In Progress, In Review) for contradictions and stale data. This is essentially code review applied to project planning.</p>