loopstack OS
Free prompt highlights
This prompt doesn't just write the plan.
It audits it until it holds up.
Stop getting plans that read like a paragraph. Read-only until you approve.
Stop briefing Claude every morning.
An automated loop that reads your project files, surfaces what's unfinished, and drops a brief to your working folder before you even wake up. Runs while you sleep so you jump straight into the work.
You're losing context every time you close a tab.
This catches it.
Paste it at the end of any Claude session, the decisions, what got dropped, what's still open, and a clean handoff for the next chat.
loopstack OS
I run every project from one folder. The loops keep it running. Six projects, one workspace, and a system that starts every session already knowing where things stood.
An OS is just the part that holds the thread for you.
- Six projects, one workspace. Every morning started the same way, re-reading my own files to remember where things stood.
- Every session with Claude starts from zero. The work is fine. The thread between the work is what gets lost, and you are the only thing holding it.
- You could build the setup yourself over months of evenings. I did. This is the packaged version.
Set it up once and every session starts already knowing.
The list is the surface. The judgment is the product.
A prompt pack is text you paste, and it forgets you the moment the chat ends. What makes this an operating system is the discipline every one of the 21 stacks shares underneath. Five decisions run through all of them.
- IT NEVER ACTS. Every stack reads and drafts. Nothing sends an email, spends money, cancels, or deletes on its own. Hitting send is always yours, so you can hand it real work without handing it the keys.
- IT NEVER DELETES. When it files something, it moves the original to a recoverable place, and only after it has verified the copy landed. Clearing that safety net is your call, never its own. A move is preserving.
- IT PRESUMES NOTHING. Setup asks what you want it for and builds only that. Someone who just wants to organize is never asked about publishing or a posting cadence. The system fits you instead of the reverse.
- IT RECONCILES ITS OWN MEMORY. A profile and a memory carry who you are between sessions, so you stop re-explaining. And a note it already resolved on your disk gets checked and dropped, never raised at you a second time.
- IT ONLY TUNES UPWARD. One stack rewrites the others against their own recent outputs, scoring each on whether it did its one job and whether a cold session could repeat it. The rewrite ships only if the new score beats the old one. Self-improvement that cannot quietly regress.
All 21 stacks, grouped by goal.
A stack is a ready-made prompt you run. A loop is a stack on a schedule. Setup asks what you want the system for and only switches on the groups that fit.
Each line below is an outcome, what a stack hands back to you. What a list cannot show is what every stack shares under the hood. Every one of these verifies before it moves and drops a note the moment your files resolve it. That shared discipline is what the five decisions above describe, and it is the difference between a stack and a prompt you paste.
- 01 daily briefThe morning state of every project, only what changed.
- 02 inbox processorEverything you dropped in, filed to its home and logged.
- 03 inbox triageThe pile sorted and the quick replies drafted.
- 04 spend auditA running ledger of what you actually pay for.
- 05 weekly reviewThe week's real movement, written down.
- 06 what did I missThe catch-up brief after days away.
- 07 ecosystem auditThe whole workspace checked, read-only until you approve.
- 08 improve a stackAny stack rewritten against its own recent outputs.
- 09 wrapThe session closed, memory and logs brought up to date.
- 11 relationship check-inWho you owe a reply, with the reply drafted.
- 12 revenue snapshotThe money picture on one page, weekly.
- 13 buyer follow-upThank-yous and check-ins drafted, never sent for you.
- 14 launch prep checkerThe pre-launch pass, 24 to 48 hours out.
- 15 lead follow-upWarm leads surfaced with a next step.
- 16 product review monitorWhat buyers are saying, gathered weekly.
- 21 analytics briefYour numbers read for you, weekly.
- 22 content briefThe next piece picked against what you already shipped.
- 23 content calendarThe week planned around the gaps worth filling.
- 24 content repurposerOne piece turned into the other formats.
- 25 draft in voiceDrafts that sound like you, not like a model.
- 26 voice self-improveThe voice file tuned from your own edits.
The outcomes are the pitch. The mechanics are in the box.
What you get. What you don't.
+ 21 stacks grouped by goal. Nine organization stacks always on, with content and business each adding six more when you switch those goals on.
+ A guided first-run setup that builds the workspace around your answers.
+ A voice extraction pass, so drafts sound like you. You pick what it covers.
+ A full guide with the folder map and a worked example of one project, start to finish.
+ Updates free to buyers.
– An autopilot. Nothing runs until you ask, and nothing sends or spends on its own. Every stack reads and drafts; hitting send is always yours.
– A SaaS. There is no login and no subscription. The workspace is a folder on your machine and your files never leave it.
– A prompt pack. Prompts forget you the moment the chat ends. This is the folder underneath that remembers.
– Magic. It needs the Claude desktop app with Cowork, which comes with the paid Claude plans, and it works from what you actually put in it.
One download. No login wall.
Loopstack-OS/ ✓ unzipped
├─ START-HERE.md
├─ SETUP-SHEET.md
├─ CLAUDE.md
├─ _inbox/
├─ _stacks/ (21 stacks, 3 goal groups)
├─ _resources/ (FIRST-RUN, MEMORY, GUIDE)
├─ _projects/
├─ _outputs/
└─ _archive/
Four steps. The first message is the install.
- STEP 1Buy it and download the zip. It unzips to one folder,
Loopstack-OS/. Put it anywhere you like. - STEP 2Open Cowork in the Claude desktop app and point it at that folder. That is the whole technical part.
- STEP 3Say anything. Setup starts on its own: it asks what you want the system for and builds around your answers. Your writing voice gets extracted from your own samples along the way.
- STEP 4Run a stack when you want the work done. Or say
"schedule the weekly review every Monday"and it runs as a loop.
No terminal and no API keys. If you can point an app at a folder, you can run this.
Who this is for. Who it's not.
- + Multi-project operators running more than one person should. Building the next thing before the last one ships.
- + Notion refugees, Linear refugees. Already living in files. They want the whole operation in one folder, not another login.
- + Anyone whose work lives in files. You don't have to make content or sell anything; organizing is a whole goal on its own.
- – Anyone running a single project. The system earns its keep across many.
- – Anyone who wants a prompt to paste. This is the folder underneath, not a snippet.
- – Anyone who won't say one first message. Setup runs itself from there, but you do have to start it.
$79 once. The whole system.
- Loopstack OS$79
- SubscriptionNONE
- Refund window30 days
- UpdatesFREE
Requires the Claude desktop app with Cowork. Cowork comes with the paid Claude plans, so the $79 assumes you already have a paid Claude subscription. Nothing else to buy from me and nothing to keep paying for.
<you> is this just a prompt pack?
<luckyd3v> no. a prompt is text you paste into one chat. loopstack OS is the workspace Claude reads every session: the 21 stacks plus the files that hold state between sessions.
<luckyd3v> it runs your whole workspace, not a single conversation.
<you> do I need to be technical?
<luckyd3v> no. there is no code anywhere in it. you add a folder to Cowork and say anything. setup runs by itself and builds the workspace around your answers.
<you> does it run on my setup?
<luckyd3v> it runs in Cowork, part of the Claude desktop app. during setup you name what you make and what you sell. the stacks read that profile and run on your projects instead of mine.
<you> what if I only want the organizing part?
<luckyd3v> then that is all it sets up. nine organization stacks are always on. content and business each add six more, only when you switch those goals on. say add content later and it sets up just that.
<you> can I edit the stacks?
<luckyd3v> yes. every stack is a plain markdown file you can read and rewrite. one of them, Improve a Stack, rewrites any other against its own recent outputs so the system tunes itself to how you actually work.
<you> does it send my files anywhere?
<luckyd3v> no. the workspace is a folder on your machine and the stacks run in your own Cowork session. every stack reads and drafts. nothing sends or spends on its own, that always waits for you.
<you> will it go out of date as Claude changes?
<luckyd3v> the stacks are instructions about how your workspace runs, not one model's tricks. new model, same folder. updates ship free to buyers.
<you> could someone copy this page and rebuild the system?
<luckyd3v> they could copy the words. the words are not the product. what you buy is the judgment inside each stack — when it refuses to act and how it verifies before it moves a single file. that took months of running my own work through it to get right.
* you are now talking in #loopstack
One folder.
Every project.
STOP: 0x0000LUCK (0xD3V, 0x00, 0xFREE)
The standalone loops live free on the prompts page. Run one before you buy the whole system. (Y/N)