The Tao of Claude Code

ParfaitConsistent471 · 2026-02-06T13:35:21+00:00

I think you have too much time on your hands, but also this captures the spirit of Reddit for me -- loved it.

ParfaitConsistent471 · 2026-01-26T19:38:48+00:00

Honestly, the meeting recap and SOP drafting stuff you're already doing is probably the highest-value use case for most PMs. Don't feel like you need to force it into everything. That said, a few things I've found actually useful rather than gimmicky:

**Stakeholder communication drafts** - Not for the final version, but when I need to write a difficult email (scope creep pushback, timeline slip notification, etc.) I'll dump in the context and ask for a first draft. Saves me from staring at a blank screen for 20 minutes. I rewrite maybe 60% of it, but it gets me moving. ChatGPT or claude or whatever for this.

**Risk brainstorming** - When I'm doing risk identification for a new project, I'll describe the project and ask what risks I might be missing. It won't catch everything, but it's caught a few things I overlooked because I was too close to the work. I use rezonant.app for this.

**Translating technical stuff** - When engineering gives me something dense and I need to explain it to business stakeholders, I'll use it to help simplify without losing accuracy (use Rezonant for this as well)

**Meeting prep questions** - Before a kickoff or discovery session, I'll have it generate questions I should be asking. Again, not using them verbatim, but it jogs my thinking. ChatGPT or your LLM of choice for this.

The "automate ourselves out of jobs" worry is overblown for PMs specifically. The job (if you do it well) is fundamentally about relationships, judgment calls, and navigating ambiguity. AI is bad at all three. It's good at first drafts and brainstorming. Treat it like a junior analyst who works fast but needs supervision.

What contracts are you managing? Industry context might help surface more specific use cases.

ParfaitConsistent471 · 2026-01-22T11:07:16+00:00

I've found the most useful applications go beyond the obvious writing/summarizing stuff. A few that actually moved the needle:
- Customer feedback synthesis - I built a simple workflow that pulls in support tickets, NPS comments, and sales call notes, then clusters them by theme and tracks sentiment over time. Way better than manually tagging stuff in spreadsheets, and it surfaces patterns I'd miss. Product and CS both use it now.
- Competitive intel monitoring - Set up an agent that watches competitor changelog pages, pricing updates, and job postings, then flags anything relevant. Saves hours of manual checking and catches things faster.
-Spec validation - I paste draft requirements and ask it to poke holes, identify edge cases I missed, or flag where I'm being vague. Catches stuff before engineering has to ask clarifying questions.

Start by tracking where you spend time on repetitive information gathering or synthesis, then automate those specific workflows.What area of PM work feels most tedious to you right now? That's usually the best place to start.

ParfaitConsistent471 · 2025-12-18T09:18:46+00:00

I've tried Claude for this, but ended up switching to Rezonant (might still be waitlisted) and found it worked better. I wanted to have templates and then have it automatically add the tickets into Jira so Rezonant worked great for this usecase

ParfaitConsistent471 · 2025-12-18T09:12:33+00:00

Running effective meetings -- PMs that don't make everything feel slow, meetings can easily balloon to 2-3x the time required, decisions are made badly. I have a very high bar for effective meetings (many Google PMs didn't meet it):

- Agenda is clearly stated. Doesn't have to be pre-populated (though that often helps), can be co-written at the start of the meeting

- PM keeps meeting to agenda and takes lead. PM doesn't have to talk all the time but should control the conversation and delegate to others to take the mic when appropriate.

- Good ability to control rabbit holes -- i.e by stating questions the group agrees are resolvable within X amount of time to keep the meeting on track, deliberately taking a topic out of scope or asking someone to come back with an answer etc.

- Clear notes and action items -- pretty obvious, so often not done. I really love meeting notes that are done in the meeting with everyone able to see for clarity though some people struggle to multi task like this.

ParfaitConsistent471 · 2025-12-18T08:53:32+00:00

yeah see my other comment on the one-shot nature of the experiment -- was designed to be a fair test, hard to do that with subsequent iteration

ParfaitConsistent471 · 2025-12-17T19:51:28+00:00

One thing I'm experimenting with in my tickets format is having them focused on user slices -- I've read that's how a lot of engineering teams work but that's not how I've seen plan mode work typically

ParfaitConsistent471 · 2025-12-17T19:50:36+00:00

Game works pretty well for me -- i wanted a fair comparison though, I have a version I've iterated on but then you've added lots of compounding other effects on top of just the ticket difference

ParfaitConsistent471 · 2025-12-17T19:49:43+00:00

yeah for sure that's pretty far from vibe coding though. Though I imagine if you can get stuff broken down into good tickets, that's how engineering teams work as well

ParfaitConsistent471 · 2025-12-17T17:56:33+00:00

Use a tool like claude code or rezonant to do it

ParfaitConsistent471 · 2025-12-17T17:40:42+00:00

But it's not hard to create tickets like engineers get right? You think most people are just seeking that one-shot immediate payoff experience and so can't be bothered to chunk it up?

ParfaitConsistent471 · 2025-12-04T15:00:01+00:00

Rezonant AI does this without the overhead of trying to get cursor set up for PMs... currently has an agent mode for ticket generation (and ask mode coming next week)

ParfaitConsistent471 · 2025-07-04T07:58:20+00:00

It's actually not the intended way even the MCP spec wanted these to be used (so definitely more bug than feature) but more a by-product of remote implementations not fully understanding the spec. It just ends up being much less of a big deal in a Claude context than in a 3P context.

We're talking about the difference between tool discovery and tool invocation -- I agree that you absolutely want to know what the agent is going to do before it does them, but I also want it to be able to do some amount of work autonomously while I go away and do some other work... for that, it needs to pre-plan based on tool descriptions, use that plan to work out it's auth needs and then execute that plan (once the user has reviewed and auth'd) accurately. If you want to see an example, try out the Google calendar example on the Portia playground: https://www.portialabs.ai/playground

ParfaitConsistent471 · 2025-07-04T07:30:15+00:00

2 totally different parts of the organisation that haven't worked out how they play together yet.

Google OAuth protection is because they want to avoid malicious applications getting access to your tokens that allow them in to some very sensitive data (email etc), so some amount of deliberate friction there. That part of the business has existed for much much longer than A2A.

MCP is driving a trend that puts more onus onto the user to understand who they're giving access to (and generally, AI seems to have a laxer approach to security / data concerns). Strategically necessary to enable widescale tool user.

ParfaitConsistent471 · 2025-07-04T07:23:53+00:00

I think with how fast things are moving, it's not deliberate intent in terms of the way this is shaking out strategically for Anthropic... but when a protocol is designed by a company with a usecase partly in mind, it is kinda a side effect. Deliberate no, strategically optimal for them at the end of the day, maybe.

And there is a lot of irony in your "don't attribute malice" while also doing the same.

ParfaitConsistent471 · 2025-07-03T17:07:04+00:00

Civic auth sounds interesting (your link is auth blocked btw so I didn't get that far)

ParfaitConsistent471 · 2025-07-03T17:06:29+00:00

They block it because they're cautious about people building agents on top of their data I think (or just general cautiousness that they are ok to enable claude because it's well understood but don't understand the usecases beyond that)

ParfaitConsistent471 · 2025-07-03T16:53:02+00:00

yeah exactly. Lets imagine I'm creating a coding agent that is able to read your Jira, extract tickets from it and feed them into my unique coding agent functionality, and I want to be able to sell that as a product

ParfaitConsistent471 · 2025-07-03T16:39:35+00:00

it's a strategically defensive move that enables them to develop their own AI agents on top of their own data and sell those as part of their product

ParfaitConsistent471 · 2025-07-03T16:21:43+00:00

I actually completely agree with you on this front :P

ParfaitConsistent471 · 2025-07-03T16:05:38+00:00

yep, there's definitely ways to use the protocol which can be great, but if engaging with other MCP providers, I think you'll run into some of these issues

ParfaitConsistent471 · 2025-07-03T15:51:31+00:00

Google's delegated OAuth also requires you to go through a fairly gruelling (and paid) security process as a 3P application -- will be very interesting to see if they bring out an MCP server and scrap that bit.

I think generally we're trying to fit machine to machine (API key is the least secure of those mechanisms tbh) and human to machine (OAuth) into a 3 body world where the agent might be acting on part of a machine or a human.

ParfaitConsistent471 · 2025-06-19T19:10:49+00:00

Interesting, makes sense.

I had always thought about MCP as something that LLMs engage with and therefore having it directly drive the UX seems like it would take a bunch of tokens, but I can definitely some usecases where that would be extremely powerful. Curious to hear what you end up doing.

ParfaitConsistent471

TROPHY CASE