Stories

Wiki-driven development: coding agents update a wiki for you, you set direction

Article news.ycombinator.com

Wiki-driven development: coding agents update a wiki for you, you set direction

My team has been working in a way we are calling calling wiki-driven development, where the wiki is written for the human, not the agent and the human uses primarily the wiki to set direction for the agent. This is different from Karparthy's LLm I'm curious whether others do something like it.

Once I run several coding agents at a time, I get overwhelmed and disorganized. Every session makes decisions and raises questions, and I can't reread the transcripts. CLAUDE.md and agent memory help the agent, but they don't give me a place to see what is going on and decide. The problem gets worse with a team.

So, I have the agents write a wiki, and they write it for me. As they work, they record only what is significant: decisions with who made them, when, and the option we passed over; open questions with an owner; and a short summary of where each area stands. I ask it to focus on the big picture, strategy, key architectural or business decisions.

In more detail: 1. Agents do the work and update the pages it affects with what is significant: key decisions, key strategic points, open questions, and a summary of where things stand. 2. I read the wiki to understand the big picture: the key points, where we are, and what still needs to be decided. It is short enough to read. 3. I think and decide there: I settle a question, change a decision, lay out some more strategy points, or rewrite a page to say where I want to go. 4. The next session builds from the page I changed.

Karpathy's LLM Wiki idea is related, but it compiles sources you collect into a knowledge base that keeps getting richer. His goal is completeness for research. Our approach is minimalistic: the pages distill way down from the agents' sessions, hold only what is significant, and exist only so I can think and decide.

Spec-driven development has you write the spec up front for the agent to implement. Here the agent writes the wiki based on all the valuable detail that are in my session prompts and its response and I edit the wiki, so the document keeps up with the agents work and my job is thinking, organizing, deciding, direction.

Here are some things I have learned doing this: - Organization is key for me as the human. I make the agent make a nice visual html with clickable links marketecture or architecture or business model canvas as the top page and navigate from there. I have it keep each page a page long so I actually am motivated to read stuff. - Have the decisions record the rejected options, so when someone brings a question back, the reasoning is available. We are constantly revisiting decisions as we work and learn and so this is very helpful. - The agent wants to write everything down. The criteria I give it is to only record what it would need to get back to where we are right now in terms of strategy, decisions, implementation. Its not that much.

You can do the same with a CLAUDE.md that tells the agent what to record, and work in markdown files or Obsidian or Notion. We got so into this that we turned it into a free, MIT-licensed plugin for Claude Code and Codex that keeps the wiki as markdown files in your repo and lets you see the wiki in your browser locally: https://github.com/nimbalyst/nimbalyst-wiki.

Do you work in this way? If so, what other things should we be doing and how have you made it work well?

Discussion 1 comments · 4 points · wek · 13h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    [ / ]
    Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.