| ▲ | arjie 16 hours ago |
| I could not produce useful output from this. It was useful as a rubber duck because it asks good motivating questions during the plan phase, but the actual implementation was lacklustre and not worth the effort. In the end, I just have Claude Opus create plans, and then I have it write them to memory and update it as it goes along and the output is better. |
|
| ▲ | hatmanstack 15 hours ago | parent [-] |
| No brother, the Claude plans aren't the right path, they're for hobbyists. |
| |
| ▲ | arjie 15 hours ago | parent [-] | | Okay, I'll give these another shot. Perhaps I just haven't figured out how to use them right. | | |
| ▲ | hatmanstack 15 hours ago | parent [-] | | I don't know brother, I don't use them, they may be great they may suck. What I've found is that adding peripherals always creates more problems. If you aren't using Claude for professional work then just sticking with the factory plan mode probably works. If not, look into creating your own Claude skills, try to understand how prompt pipelines work and it will unlock a ton of automation for you. Not just for coding. | | |
| ▲ | arjie 14 hours ago | parent [-] | | I do use Claude for professional work, but I suspect I don't know enough to be able to get anything useful out of your advice since I don't know how to add my own Claude skills that form a prompt pipeline without adding peripherals. I'll just have to catch this part of the whole thing as a late adopter, I suppose. Ah well, thanks for the help. | | |
|
|
|
