4 ms·

I like the best of both worlds approach of asking Claude to refine a spec with me (specifically instructing it to ask me questions) and then summarize an implem

I like the best of both worlds approach of asking Claude to refine a spec with me (specifically instructing it to ask me questions) and then summarize an implementation or design plan (this might be a two step process if the feature is big enough) When I’m satisfied with the spec, I turn on “allow all edits” mode and just come back later to review the diff at the end. I find this works a lot better than hoping I can one shot my original prompt or having to babysit the implementation the whole way.

wahnfrieden 1y ago
I recommend trying a more capable model that will read much more context too when creating specs. You can load a lot of full files into GPT 5 Pro and have it produce a great spec and give more surgical direction to CC or Codex (which don’t read full files and often skip over important info in their haste). If you have it provide the relevant context for the agent, the agent doesn’t waste tokens gathering it itself and will proceed to its work.
- boredtofears 1y ago
  Is there an easy way to get a whole codebase into GPT 5 Pro? It's nice with claude to be able to say "examine the current project in the working directory" although maybe that's actually doing less than I think it is.
  - simonw 1y ago
    I wrote a tool for that: https://github.com/simonw/files-to-prompt https://github.com/simonw/files-to-prompt - and there are other similar tools like repomix. These days I often use https://gitingest.com https://gitingest.com - it can grab any full repo on GitHub has something you can copy and paste, e.g. https://gitingest.com/simonw/llm https://gitingest.com/simonw/llm
    - boredtofears 1y ago
      Of course you did - thanks, huge fan!
    - dist-epoch 1y ago
      I wrote a similiar tool myself, mostly because your tool or repomix doesn't support "presets" (saved settings): [client] root = "~/repo/client" include = [ "src/**/*.ts", "src/**/*.vue", "package.json", "tsconfig*.json", "*.ts", ] exclude = [ "src/types/*", "src/scss/*", ] output = "bundle-client.txt" $ bundle -p client What do you do when you repeatedly need to bundle the same thing? Bash history?
      - Xorakios 1y ago
        omg you rock!

wahnfrieden 1y ago

I recommend trying a more capable model that will read much more context too when creating specs. You can load a lot of full files into GPT 5 Pro and have it produce a great spec and give more surgical direction to CC or Codex (which don’t read full files and often skip over important info in their haste). If you have it provide the relevant context for the agent, the agent doesn’t waste tokens gathering it itself and will proceed to its work.

boredtofears 1y ago
Is there an easy way to get a whole codebase into GPT 5 Pro? It's nice with claude to be able to say "examine the current project in the working directory" although maybe that's actually doing less than I think it is.
- simonw 1y ago
  I wrote a tool for that: https://github.com/simonw/files-to-prompt https://github.com/simonw/files-to-prompt - and there are other similar tools like repomix. These days I often use https://gitingest.com https://gitingest.com - it can grab any full repo on GitHub has something you can copy and paste, e.g. https://gitingest.com/simonw/llm https://gitingest.com/simonw/llm
  - boredtofears 1y ago
    Of course you did - thanks, huge fan!
  - dist-epoch 1y ago
    I wrote a similiar tool myself, mostly because your tool or repomix doesn't support "presets" (saved settings): [client] root = "~/repo/client" include = [ "src/**/*.ts", "src/**/*.vue", "package.json", "tsconfig*.json", "*.ts", ] exclude = [ "src/types/*", "src/scss/*", ] output = "bundle-client.txt" $ bundle -p client What do you do when you repeatedly need to bundle the same thing? Bash history?
    - Xorakios 1y ago
      omg you rock!