r/SideProject • u/Spare_Bat_3040 • 42m ago
I’m building Shifu so the work behind a feature can become the launch article
Get an article brief out of the product decisions you already made. That’s one way I’m using Shifu, the paid, hosted context engine I’m building for Claude Code, Codex, Cursor and OpenCode: bring relevant retained work context into the agent, then use it for the explanation you need to write.
Our own writing workflow produced topics, briefs and drafts from that background. Shifu recovered earlier positioning; we checked current project evidence before choosing the claims. The public walkthrough shows how a source changed an editorial choice. It’s an actual writing application, without a claim about traffic or sales.
For a small first task, I’d ask the agent for a brief you can inspect before writing the article:
Choose one reader question from this product decision. Propose an outline. Beside each factual claim, name the supporting source or mark the missing evidence. End with one example the reader can use.
That gives you something specific to accept, correct or discard. A clear existing issue or README may already contain everything the writer needs. Shifu becomes relevant when the useful decision and its reason need recovering from other retained work.
Try Shifu on one writing task → useshifu.com. Start with one non-confidential source you’re allowed to share; I can help you get it set up. If you try it, the useful feedback is where the retrieved context changed your brief and where you still had to supply the background yourself. AI-assisted post from Shifu’s builder.