4 ms·

What does this do better than just asking your agent to "write docs" or a more robustly defined prompt/skill?

• _pdp_ 3mo ago
  This is what we do. The same agent writing the code can also write the docs.
• b212 3mo ago
  I swear most of these tools are made for the sake of it… While good old prompting is often better than plan mode or superpower skills.
  • SpicyLemonZest 3mo ago
    I've had a number of people send me tools like this at work, and easily 50% of them can't answer basic questions like "what's the reason someone would adopt this tool" or "how do you know that it will achieve its stated goals". Agents are good at reading code, I can't imagine what the point of autogenerating agent context could be if it's not showing demonstrable cost benefits.
    • sdesol 2mo ago
      > I can't imagine what the point of autogenerating agent context could be I have a fork of the OpenAI Codex repo at https://github.com/gitsense/smart-codex https://github.com/gitsense/smart-codex that shows why you may want to autogenerate agent context. I makes navigating a 4000+ file repo extremely context efficient. It is important to note that the goal is too keep the context as clean as possible and not necessary speed.
• capplexham 3mo ago
  Have a look at the prompts in the GitHub [0]. It defines a System Prompt and specifies the documentation structure. This would allow you to switch coding agents, instead of relying on how your coding agent interprets the command "write docs". [0]: https://github.com/langchain-ai/openwiki/blob/main/src/agent/prompt.ts https://github.com/langchain-ai/openwiki/blob/main/src/agent...
  • LudwigNagasena 2mo ago
    That's just cruft unless there is a benchmark demonstrating it's actually better than just asking an agent to write docs and/or using one of the thousands of document-writing skills like Anthropic's doc-coauthoring.