Chatbot Q3 2026 Code Readiness
Open-contributor bucket for independently pullable improvements to the squad's development and internal operational surfaces. Puji Triwibowo owns routing and bucket health as EM; delivery ownership stays with the people named on each story.
Routing charter
This bucket includes repository workflows, tests, MCP integrations, hooks, agent skills, and minor internal operational/admin tooling. Systemic runtime, framework, dependency, security, reliability, performance, or architectural modernization belongs in Chatbot 26Q3 Engineering Initiatives. Customer-facing outcomes belong in their product initiative.
When work has independently deliverable outcomes in more than one category, split it into separate stories. Otherwise route by the primary outcome. The durable decision and examples are recorded in ADR 0001.
Scope Changes
- Backend
- Frontend
- Docs
Stories — per-story tracker (canonical)
| Story | Class | DRI | Status | Added | Scope | BE | FE | QA | Jira Story | Summary (→ PRD) |
|---|---|---|---|---|---|---|---|---|---|---|
| A1 | 🟡 Standard | samudra.linggar | backlog | 2026-07-02 | Frontend | — | samudra.linggar | — | BOT-4501 | CR-S01 — Repository MCP Improvement → PRD |
| A2 | 🟡 Standard | baghiz.firdausa | backlog | 2026-07-02 | Frontend | — | baghiz.firdausa | — | BOT-4502 | CR-S02 — Repository Testing Improvement → PRD |
| A3 | 🟡 Standard | — | backlog | 2026-07-02 | — | — | — | — | BOT-4504 | CR-S03 — Repository Hook Improvement → PRD |
| A4 | 🟡 Standard | baghiz.firdausa, samudra.linggar | backlog | 2026-07-02 | Frontend | — | baghiz.firdausa, samudra.linggar | — | BOT-4505 | CR-S04 — Repository Agent Skill Improvement → PRD |
| A5 | 🟡 Standard | farras.herdicho | in-progress | 2026-07-24 | Backend | farras.herdicho | — | — | BOT-4742 | CR-S05 — Internal Tooling Improvement → PRD |
Progress rollup: 0 of 5 done (0%) as of 2026-07-24. Tracker status mirrors Jira and is not inferred from linked Task completion.
Pull rule
The bucket is classed, not ranked. Standard and Intangible stories fill available capacity without displacing ranked product work. Expedite may preempt only when authorized, entered in the Expedite log, and within the declared WIP limit.
A story is pull-ready only when its actual Scope and owners are recorded. Any discipline may contribute. Add QA to Scope and name the QA contributor when QA participates; a story without QA scope does not require a standing QA owner.
Expedite log
| Story | Date | Authorized by | Preempts | Reason |
|---|---|---|---|---|
| — | — | — | — | No Expedite story currently classified. |
QA Lane
Lane B is the conservative release-validation default, not a permanent staffing assignment.
Each story records actual contribution. When manual QA is needed or QA contributes, add QA to
Scope, name the QA owner in the tracker, and mirror that allocation in team capacity before pull.