Chapter 1
Keep Jira as it is
Picture a product team: iOS, Android, backend, a tech lead, a solution architect, and QA. Their backlog already lives in Jira. CatAgent connects to that Jira project and its code repositories without asking anyone to learn a new board or move their tickets somewhere else.
Chapter 2
Plan in Jira first, code per repo second
One Jira Epic usually spans three different repositories (iOS, Android, and Backend). If a coding agent jumps straight into writing code from a raw PRD, a single wrong assumption breaks three codebases at once.
CatAgent splits the work into two phases. First, at the Epic level, an Architect (SA) agent breaks the PRD into child Jira tickets and a QA agent writes the manual test cases—without touching any code repo. Once a human Architect and Tech Lead approve that plan, the Story level starts in each platform's own repo: a Tech Lead (TL) agent writes the technical spec and unit tests first, and an Engineer agent writes the code to pass them.
Split PRD into stories
Jira only · 0 code changed
Agents read the Epic PRD and split it into platform tickets (PAY-142 iOS, PAY-143 Android, PAY-144 Backend) plus a manual QA checklist. Zero code repositories are touched yet.
Created ticket PAY-142 (iOS): Biometric PIN fallback
Created ticket PAY-143 (Android): BiometricPrompt fallback
Created ticket PAY-144 (Backend): Lockout token API
⏸ Paused — waiting for Human Lead to approve plan
Chapter 3
A branch, not a pull request
When most coding bots finish a task, they immediately open a pull request and tag four teammates to review 1,000 lines of code nobody on the team has ever run. Everyone ends up debugging raw bot output in PR comments.
CatAgent turns automatic PR creation off. When the Engineer agent finishes, it pushes its commits to a side branch called pipeline/PAY-142. The human engineer assigned to the ticket checks out that branch on their laptop, runs it, fixes any rough edges in their own commit, and opens the pull request only when they stand behind the code.
Biometric PIN fallback
Engineer checked out branch, tweaked 1 line, then opened PR
Chapter 4
Measuring what sticks
Because the agent commits its work first and the human engineer commits their review edits second on the same branch, Git keeps a permanent record of who wrote every single line. That lets CatAgent's Insights dashboard answer four practical questions automatically:
- How much agent code survived untouched? If the agent wrote 5 lines and the engineer only changed 1 line before merging, the survival rate is 80% (4 out of 5 lines).
- Were the unit tests good? Whether the engineer kept the agent's unit tests as-is or had to rewrite them.
- Did it actually save time? How many minutes the engineer spent reviewing the branch before opening the PR.
- If a bug appears later, who caused it? Running
git blameon any bug fix tells us immediately whether the bug was in an untouched agent line or in a line a human edited during review.
func verifyBiometric() async throws -> AuthState {
guard sensor.canEvaluateBiometrics() else {
return try await pinScreen.present(maxAttempts: 3) // human tweaked
}
return try await sensor.authenticateUser()
Written by the Engineer Agent on pipeline/PAY-142 to conform to BiometricAuthService protocol. Merged with zero human alterations.
80% survived untouched
4 lines written by the agent were good enough to ship to production without any human edits.
Only 1 line needed a tweak
The engineer only changed line 3 to set maxAttempts: 3 on the PIN fallback screen.
Knows who wrote the bug
If QA finds a bug on line 3 tomorrow, CatAgent knows it came from the human edit—not the agent.
Chapter 5
CatBoard
CatBoard helps one engineer run parallel agents on their own machine. CatAgent is the team-wide pipeline on top of the Jira epics they already share. I compare both setups in my research note on human gates.