PMs using versioned repos
A social post highlights growing use of version-control-style repos for product teams—where strategy docs and PRDs live in shared, versioned stores with automated Slack PRs—suggesting non-engineering roles are adopting code-like workflows for durable context. Another post advises choosing vendors with built-in product discipline to avoid slowdowns when building industrial AI. (x.com (x.com)
Product managers are starting to run strategy documents like code, with requirements, launch plans, and notes stored in versioned repositories instead of scattered files. (news.aakashg.com) Aakash Gupta published an April 7, 2026 interview with DoorDash product manager Hannah Stulberg describing a “Team OS” in Claude Code, where a product manager checks “every document, every metric, every customer call” into a shared repository. (news.aakashg.com) GitHub’s own documentation describes a repository as a place to store files and their full version history, with branches for parallel work and pull requests to propose and review changes before they reach the main branch. (docs.github.com) That workflow is moving beyond software code because product teams also produce files that change over time: product requirements documents, objectives and key results, launch plans, and sprint reviews. Gupta’s public GitHub setup for product managers includes templates for all four. (github.com) The appeal is durability. A versioned repository keeps earlier drafts, review comments, and final decisions in one place, instead of splitting context across Google Docs, Notion pages, chat threads, and ticket systems. (docs.github.com; github.com) Slack is part of the pitch because review workflows only work if people see them. Slack’s GitHub app says it can preview pull requests and issues inside channels, and it uses OAuth so actions such as opening pull requests or commenting are tied to a user’s GitHub identity. (slack.com) GitHub documents pull requests as a place where collaborators can comment on specific file changes or leave general feedback on a project. In a product setting, that turns a requirements update into something closer to an engineering review than a meeting note. (docs.github.com) The other half of the argument is operational. Stuart Wilson wrote in a July 2026 social post that companies building industrial artificial intelligence should pick vendors with product discipline built in, rather than bolt tools together and absorb the process debt themselves. (x.com) That fits the same pattern: industrial artificial intelligence projects generate fast-moving specs, workflows, exceptions, and operating rules, and those projects slow down when teams cannot track what changed, who approved it, and which version is current. GitHub’s branch protections and merge controls are built for exactly that kind of governed change process. (docs.github.com) The shift is not that product managers suddenly became engineers. It is that more non-engineering teams are borrowing engineering’s file cabinet — version history, review gates, and shared context — to keep decisions from disappearing into chat. (docs.github.com; news.aakashg.com)
