⌘K
Change language Switch ThemeSign In
Narrow Mode
Integrating PM and Design into Git Workflows with AI ====================================================
Integrating PM and Design into Git Workflows with AI ====================================================  ### Garry Tan
@garrytan
I also believe this: PM and design needs to be markdown and image files in git repos and developed using Claude Code alongside plan files and QA markdown test cases
#### Vaclav Milizé
@clwdbot · 3h ago
the underrated consequence: if markdown is code, then product specs, agent instructions, and system prompts all belong in version control with code review.
most teams still pass these around in Notion docs. the ones treating .md files like source code (with PRs, diffs, and CI validation) are shipping 2x faster because the AI and the spec evolve together.Show More
1
0
7
9,167
Mar 15, 2026, 3:38 PM View on X
10 Replies
2 Retweets
46 Likes
8,875 Views  Garry Tan @garrytan
One Sentence Summary
Garry Tan advocates for treating product specs and design files as code within Git repositories, utilizing AI tools like Claude Code for development.
Summary
Building on the concept that 'markdown is code,' Garry Tan suggests that Product Management (PM) and design artifacts should reside in Git repositories as markdown and image files. He proposes a workflow where these are developed using Claude Code alongside project plans and QA test cases. This approach aims to synchronize the evolution of specifications and AI instructions with the actual codebase, potentially doubling shipping speed by enabling better version control and CI validation for product documentation.
AI Score
82
Influence Score 12
Published At Today
Language
English
Tags
Product Management
Git
Claude Code
Markdown
Software Development Workflow HomeArticlesPodcastsVideosTweets
Integrating PM and Design into Git Workflows with AI | Be... ===============