VibeCheck: workflow triage for teams shipping AI-written code
Redesigns process and metrics for teams that code with AI
- Problem
- Teams still run the old playbook of backlogs, estimates, iterations, feature teams, and PR reviews, but AI-written code leaks through all of it and many rituals no longer make sense, with no clear replacement. Meanwhile projects silently run for an hour or more because the agent keeps adding serially executed tests and nobody has the metrics to catch it.
- Solution
- A lightweight diagnostic tool that pulls GitHub/GitLab data (PRs, review times, CI duration, commit patterns) plus a short team survey to find which workflow steps AI-generated code has slowed down or hollowed out. It outputs an actionable list of process changes, such as risk-based review paths, test parallelization, and estimation replacements, with monthly re-runs to track progress.
- Users
- Engineering teams of 10-100 people and their managers who already use AI coding heavily
- MVP
- GitHub integration that computes 5-8 key metrics automatically; a 10-minute team survey; a one-page process recommendation report; monthly re-tests for comparison
- Revenue
- Subscription by team size; consulting add-on packages
- Why now
- AI coding is widespread but team organization hasn't caught up and managers are actively asking how to change; all the data lives on GitHub and is directly readable by a solo builder
Source discussions · 2
- Hacker NewsAsk HN: How to organize teams to ship AI-written code?1↑ 0
- V2EX[分享发现] 一个 AI 耗时过长的原因