DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a project through an Inputs, Process, Outputs pipeline with Second Brain OS

Give one project its own CLAUDE.md and a four-stage folder pipeline the agent follows.

  • Research
  • Intermediate
  • 60 minutes
  • From the README
  • Claude Code

Who it is forA writer, engineer or student who is about to ship one piece of work and wants the agent to use the vault's notes while doing it.

The problemProject notes live apart from what the agent knows, so each session starts from zero and the work drifts from the source material.

The outcomeA scoped project folder with its own CLAUDE.md and Inputs, Process, Outputs and Feedback stages that draws on the wiki and feeds results back into it.

What you need first

  • Git, to clone the repo
  • Obsidian, to open the vault as a folder
  • Claude Code, the agent the README sets up the vault around
  • A terminal, for the copy commands and for running claude

Steps

  1. Complete the vault setup from the first use case so ~/brain exists with .claude and scripts in place
  2. Create one project folder inside ~/brain for the work you are shipping, following the project pipeline in vault-template (inferred, check the README)
  3. Add a CLAUDE.md in that project folder that states its goal and points to the relevant wiki pages (inferred, check the README)
  4. cd ~/brain && claude and work through the project's Inputs, Process, Outputs and Feedback stages in order
  5. Record the outcome in the Feedback stage so the next session can read it

Prompt for your agent

In the second-brain-os vault at ~/brain, work inside the <project-folder> project using its CLAUDE.md and its Inputs, Process, Outputs and Feedback folders. Produce the project's output file and note what changed in Feedback. Verify that the output cites at least two existing wiki pages.

Caveat. The README describes the project pipeline in general terms, so the exact folder names and file contents should be taken from the vault-template files rather than assumed.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page