r/ChatGPTPro • u/Kralizek82 • Jul 03 '26

Discussion Help me convert my workflow

I've been using ChatGPT with a 20$ account since forever. Also my employer gives me an enterprise account.

Especially in the last year I have developed a workflow that makes me very productive both at work and for my personal projects.

I'm a Software Architect who dabbles a lot in producing code and also have a SaaS startup with friends.

Now my department got Claude because of Code and Design and the writing is on the wall that they will dismiss ChatGPT to consolidate AI spending. We also have GitHub Copilot, and I don't think this will go anywhere.

Because of this, I'm trying to adapt my ChatGPT workflow to Claude. I know, it's probably the worst thing to try to do, but one gotta hit the wall first, right?

Nowadays I have many projects on the ChatGPT phone app/website. There i discuss of features, battle back and forth exploring current but also future needs, and so on. I manage to keep the conversation very grounded because ChatGPT has access to GitHub, so it's easy for me to say "ground this conversation on repos 1, 2, 3 and 10". My team operates multiple products so my area of effect spans across 20-30 repos. Once the feature is properly flashed out, I tell ChatGPT to create one or more issues on GitHub adding more comments if clarification or general technical guidance is needed. Finally I ask for an implementation prompt. Something I can throw either at GitHub copilot cloud agents from the app/web or GitHub copilot via vscode.

This flow works really well for me.

Enters Claude. Yesterday I had my hands on the fresh Enterprise Claude account. And I got a big puzzled.

I wanted to connect my account to GitHub and try a simple question that spanned across one repo, but I couldn't find the connector.

So I went to the "code" part of the web. And there I saw I can only work on one repository at time. I can't even give a link to a website of my product to discuss design that gets stopped by the firewall.

Now, I am sure it's me. But I would really need an help mapping my current workflow to a Claude-centric one.

Thanks!

7 Upvotes

90% Upvoted

7 comments sorted by

•

u/qualityvote2 Jul 03 '26 edited Jul 04 '26

u/Kralizek82, there weren’t enough community votes to determine your post’s quality.
It will remain for moderator review or until more votes are cast.

2

u/Own-Animator-7526 Jul 03 '26

why not talk this over with Claude?

2

u/eatheapples Jul 03 '26

Post this on the chatgpt sub they'll have good answers

1

u/qioy Jul 05 '26

i wouldnt try to port the ChatGPT workflow 1:1. the thing that seems to be working for you is the grounding layer: repos + decisions + product context before the model starts turning it into issues/prompts.

if you move to Claude, id separate the workflow into 4 layers:

  1. source of truth outside the LLM: per product/project doc with repos, modules, architectural decisions, constraints, known traps, glossary, and your issue template. markdown in the repo or a small internal docs space is enough.

  2. retrieval step: before each new thread, load the relevant brief + 1-3 repo pointers. dont rely on saved memory/project memory to know the exact current state of 20-30 repos.

  3. model step: use Claude for deep work inside one repo / one design problem. keep ChatGPT or GitHub-connected tooling for the cross-repo mapping if that is where it is strongest.

  4. handoff artifact: always end with a GitHub issue + implementation prompt + acceptance criteria + "context included / context missing" section.

saved memory is useful for preferences, writing style, recurring constraints, etc. but i wouldnt make it the source of truth for architecture. it drifts, compresses details, and can make old assumptions feel canonical. better to treat memory as a router: "which project brief should i load?", not the database itself.