Product manager, founder, builder.
I'm an independent product manager, founder, and software builder based in Kathmandu. I help teams make product decisions and adopt agentic software development, drawing on over a decade of building software. I write about product thinking, engineering with AI, and hands-on experiments.
The journey
Engineer, founder, now independent.
Over a decade building software. Selected chapters from engineering, founding, and consulting.
Software Engineer
Leapfrog Technology·2014 — 2017
Three years across Rails, React, and React Native. Trainee → Technical Project Manager.
Founder
Truemark·2017 — 2025
Founded and ran a product engineering studio for eight years. Wound it down to focus on a single product team.
Contract Software Engineer
Luthor (YC F24)·Previous engagement
Worked with Luthor as an independent contract software engineer.
Product manager & consultant
NowIndependent·Now
Freelance product management, codebase readiness audits, software factory setup, and agentic coding adoption.
Now
What I'm focused on this season.
Updated regularly · inspired by nownownow
Parallel agent coding
OpenSpec for spec-before-code, Beads as the local task graph, git worktrees for isolation. The toolkit I wish I had.
Updated May 2026
Hermes for release notes
Wiring a Hermes agent to draft release notes from commits and PRs. Cron-scheduled, model-agnostic, ~$5 of infra.
Updated May 2026
Field notes · AI & agentic engineering
On building software with AI agents.
New workshop · free, self-paced
Stop repeating yourself to your agent.
A hands-on workshop that turns the four-layer agent-ready stack into muscle memory: one prompt, one hook, one subagent, one skill, against a planted bug in a starter repo.
Hook
Block the diff before the agent finishes.
Subagent
Audit the rest of the repo for siblings.
Skill
Name the workflow so you can call it.
Listen
Latest essay, in your ears.
Audio companions to selected essays. Generated, then loudness-normalized and published as a GitHub release.
The Subagent I Didn't Need
A confession about a subagent I wrote, ran for a month, and quietly deleted — and the broader taxonomy of agent-side artifacts that helped me see why. Five things live in a mature agent-ready repo, and they are not interchangeable. A field guide to when not to delegate.
Reading paths · In-depth series
Pick a track. Each one ships a complete idea end to end.
Tech notes
From the engineer's notebook.
Patterns, debug stories, and small wins — written for my future self.
Browse all
What to Put in an AI Coding Task Brief
Keep Listening Notes Without Turning Music into Homework
Write a Bug Report That Survives the Handoff
What to Put in an AI Coding Task Brief
Give an agent an outcome, boundaries, source of truth, and acceptance evidence instead of a long list of guesses.
Keep Listening Notes Without Turning Music into Homework
Use a few concrete observations to remember an album and decide what to revisit.
Write a Bug Report That Survives the Handoff
Preserve the trigger, observed result, expected behavior, and environment without burying the next person in logs.
Match Code Review Evidence to the Claim
A test result, a screenshot, and a deployment observation each support a different kind of conclusion.
How to Keep Technical Documentation Honest
Distinguish implemented behavior, design intent, and open questions so readers know what they can rely on.
A Small Change Record That Proves What You Deployed
Capture source revision, target, running revision, and the observed user action in one compact record.
Build a Service Dependency Map You Can Use During an Outage
Map the path from a user request to persistent data, then distinguish required and optional dependencies.
Design Homelab Health Checks Around User Actions
Process, port, dependency, and transaction checks answer different questions; make the difference visible.
How to Tell Whether Scheduled Maintenance Actually Finished
Separate the timer, maintenance action, reboot, and application checks before calling an automated update successful.
Working notes
What people say after shipping together.
A few field notes from clients and peers who worked with me across product, engineering, and company-building.
Prakash and the Truemark team stand above every engineering team I've worked with over the last 25 years. If you can partner with Prakash, you will not regret it.
I have seen him progress from Trainee to Technical Project Manager. He is an excellent software developer, very enthusiastic, a quick learner, and someone with excellent problem solving skills.
Prakash is really easy to work with, and has a good understanding of react-native and javascript. I hope to work with him again one day.
Prakash and the Truemark team stand above every engineering team I've worked with over the last 25 years. If you can partner with Prakash, you will not regret it.
I have seen him progress from Trainee to Technical Project Manager. He is an excellent software developer, very enthusiastic, a quick learner, and someone with excellent problem solving skills.
Prakash is really easy to work with, and has a good understanding of react-native and javascript. I hope to work with him again one day.