Skip to main content

Chatbot Code Readiness Workstreams

Operational requirements for improving the Chatbot squad's repository workflows and internal tools without mixing that work into customer-facing product Epics or systemic runtime modernization.

Scope Changes​

  • Backend
  • Frontend
  • Docs

User Stories​

CR-S01 — Repository MCP Improvement​

As a repository contributor, I want maintained MCP integrations so routine engineering operations remain reliable and discoverable.

  • AC-1: Changes improve or repair a repository-owned MCP workflow and document how contributors validate it.

CR-S02 — Repository Testing Improvement​

As a repository contributor, I want stronger automated test coverage and test infrastructure so changes can be validated earlier.

  • AC-1: Changes add or improve repeatable automated validation for the affected repository behavior.

CR-S03 — Repository Hook Improvement​

As a repository contributor, I want useful repository hooks so common correctness checks run at the appropriate development boundary.

  • AC-1: Hook changes state their trigger, failure behavior, and a reproducible validation path.

CR-S04 — Repository Agent Skill Improvement​

As a repository contributor, I want maintained agent skills and instructions so assisted workflows follow current engineering practice.

  • AC-1: Skill changes have a defined trigger, canonical authority, and validation example.

CR-S05 — Internal Tooling Improvement​

As an internal operator, I want internal-tool lists to expose the identifiers needed for support and diagnosis without opening each record individually.

  • AC-1: The knowledge list exposes the knowledge name required by BOT-4655.
  • AC-2: The AI-agent list exposes CID as required by BOT-4656.

Non-goals​

  • Customer-facing product outcomes.
  • Runtime, framework, dependency, security, reliability, performance, or architectural modernization.
  • Normalizing Jira Story status from the status of linked implementation Tasks.