Genuinely curious: how do people write docs now that vibe coding is taking off?
Are you just talking to an agent and shipping what comes out? Or still spending real time polishing?
My current workflow:
- Start with an ambitious idea + some rough description
- Use Claude Code plugins like superpowers to break it into a concrete plan
- Let the agent generate the plan, modules, even function signatures
Two things I'm curious about:
- How does your workflow look? Do you still hand-write docs, or fully offload?
- Any tools or tricks you use to make specs more precise, or to clarify requirements before the agent runs?
Top comments (1)
As a Technical Writer, I've seen lots of generated content recently, and I must say – it's a total mess. Getting through this pile is more time-consuming and tiring than getting a concise draft or even a bullet-point list with the general idea to describe. From this, I can already create good documentation. Generated content very often contains inaccuracies that, if not checked by an engineer, can make it to the official docs and be even more harmful.
I personally use AI to polish my text. I draft the main idea, structure the document the way I want it to be structured, and then use AI to polish the text. Still, very often I need to correct it or develop a skill for it with guidelines, as it has a tendency to use overcomplicated language.