Developer Operations Copilot

Context

As NeoVista's founding software engineer, I initially prioritized shipping. As the team grew, minimal documentation made ownership, release communication, deployment context, and rotating two-week sprints harder to coordinate.

Problem

Developers preferred building to recreating information in documentation. Changelogs, review notes, deployment communication, and status updates were delayed or skipped, while daily stand-ups and long release discussions consumed synchronous time.

What I built

We built an AI-assisted workflow using GitHub Copilot, GitHub and Asana MCP connectors, GitHub APIs, Power Automate, scheduled jobs, Microsoft Teams, and custom normalization scripts. It compares planned sprint outcomes with repository activity and maintains an operational record throughout each sprint.

How it works

1. 01Read planned work, owners, deadlines, priorities, and expected outcomes from Asana at the beginning of each sprint.
2. 02Retrieve branches, commits, pull requests, reviews, repository changes, and code-owner information from GitHub.
3. 03Normalize the signals and compare recent engineering activity with the original sprint plan.
4. 04Maintain project changelogs, feature summaries, ownership records, review notes, deployment notes, release communication, task state, and potential security observations.
5. 05Send each developer a private Teams summary of completed work, outstanding responsibilities, and blockers.
6. 06Post deployment updates to the appropriate Teams group so releases and required follow-up remain visible.

Outcome

• Reduced recurring sprint meetings from five per week to two.
• Improved documentation, ownership, accountability, and sprint visibility.
• Standardized changelogs, deployment notes, and release communication.
• Reserved synchronous time for decisions, technical discussions, and real blockers.

What I learned

The highest-value developer automation often structures information that already exists. Connecting plans, code activity, ownership, and communication can improve alignment without asking engineers to duplicate their work.