justin 🌵

building

[justin 🌵 @JustinChitla]

for 7 years as a PM, I've watched the same story repeat: ambitious product roadmaps vs. the reality of limited dev resources

eventually you just accept it. the feature ideas that never make it. the "maybe next quarter" that never comes

but I've also seen what's possible with high agency product teams (look at teams like Ramp)

they don’t see this invisible separation of responsibility. both the engineering team and product team share the same passion for one thing - shipping responsible product fast

so I've been building something

It's called krosswalk - a tool that safely guides product teams to ask questions and build features in the existing codebase - NOT a prototype

ask questions, get answers grounded in the actual code

generate safe, reviewable, WORKING changes that get reviewed by your designers and product team before your engineers review and merge

PMs can finally move from "I wish we could…" to "here's a working prototype."

looking for PMs who feel this pain and want to join the next batch of users -> https://t.co/qFJ47U1Gn4

[justin 🌵 @JustinChitla]

crying tears of joy, we can finally share insta comments 🔥🔥😭

[justin 🌵 @JustinChitla]

to Instagram: plz allow me to easily share comments from reels- they are simply too good

[justin 🌵 @JustinChitla]

@SaidAitmbarek @MicroLaunchHQ thanks for your support 🙏 will check this out

[justin 🌵 @JustinChitla]

@b_migliaccio offer them a mac mini

[justin 🌵 @JustinChitla]

@_annakulina I just hate having to deal with aws bc they make it soooo hard to understand the bill and how to put a monthly spend limit

[justin 🌵 @JustinChitla]

https://t.co/UA64DwnAxU

[justin 🌵 @JustinChitla]

@SherryYanJiang super cool sherry! are you letting more folks get read access to the real repo(s) too? (for “current” prod functionality questions and better specs/prds)

[justin 🌵 @JustinChitla]

the best software teams will be made of 100% builders, differentiated less by title and more by what they optimize for: product intuition vs. systems rigor

the first wave is already here - AI coding tools like claude code and cursor are letting non-technical teammates create real things but only the most innovate teams like ramp are adopting this “all builders” mindset

this isn’t the destination! its just that current tooling is optimized for engineering workflows. the path from “i have an idea” to “this is safe to ship” is still messy.

as more of the team becomes hands-on, we need an interface that makes changes easy to preview, easy to review, and hard to mess up

https://t.co/qFJ47U2ecC is the missing interface

happy shipping ��

[justin 🌵 @JustinChitla]

prompting is writing
storytelling is writing
reading is your training data

[justin 🌵 @JustinChitla]

https://t.co/0Kaa4yhp3B

[justin 🌵 @JustinChitla]

for 7 years as a PM, I've watched the same story repeat: ambitious product roadmaps vs. the reality of limited dev resources

eventually you just accept it. the feature ideas that never make it. the "maybe next quarter" that never comes

but I've also seen what's possible with high agency product teams (look at teams like Ramp)

they don’t see this invisible separation of responsibility. both the engineering team and product team share the same passion for one thing - shipping responsible product fast

so I've been building something

It's called krosswalk - a tool that safely guides product teams to ask questions and build features in the existing codebase - NOT a prototype

ask questions, get answers grounded in the actual code

generate safe, reviewable, WORKING changes that get reviewed by your designers and product team before your engineers review and merge

PMs can finally move from "I wish we could…" to "here's a working prototype."

looking for PMs who feel this pain and want to join the next batch of users -> https://t.co/qFJ47U1Gn4

[justin 🌵 @JustinChitla]

the best pms I know are obsessed with something completely unrelated to product

[justin 🌵 @JustinChitla]

this is inspiring and exactly how I envision all ambitious product teams will work in the next few years!

I've been working on a tool called krosswalk in case there are PMs/designers that are interested in building like the Ramp team!

https://t.co/eCVEkNwwkb

[siddhi surana @justsiddaay]

This has single-handedly increased our ship velocity by 100x. As a PM, I can directly make code changes, spin up endpoints, change the FE ux, etc directly from my browser or slack. Inspect spins up a PR for my Eng team to review. My day has switched from “can you do this for me” to “can you stamp my PR” 🚀

[justin 🌵 @JustinChitla]

the single best thing you can do is constantly reset context - if you’re building a larger feature then I’ve laid out a method that works rly well here: https://t.co/IESqG0lfHG

[Cursor @cursor_ai]

Learn about how we use the filesystem to improve context efficiency for tools, MCP servers, skills, terminals, chat history, and more.

https://t.co/jLHccCwVnn

[justin 🌵 @JustinChitla]

everyone is a builder! every day is launch day! everyone ships!

[justin 🌵 @JustinChitla]

7/
the magic is the handoff:

cursor ask mode → refine requirements interactively
sprint .md files → turn plan into focused chunks
fresh claude code agents → re-check reality + execute precisely

each tool does what it’s best at

[justin 🌵 @JustinChitla]

how i’m using cursor + claude code for consistently better results:

[justin 🌵 @JustinChitla]

6/
claude code will usually spin up a few sub-agents to investigate what’s needed before implementing.

this is where the quality comes from:
smaller scope, sharper context, fewer bugs.