Capture and sort (manually or automatically) all your actions and commitments.
I have ADHD and big lists overwhelmed me, I made this highly modifiable/flexible with lots of settings to figure out what works for you.
It grows with you and you can setup what types of categories you want to prioritize.
Would appreciate any and all feedback!!
Big lists overwhelmed me, and the alternatives were costly (e.g. Omnifocus, etc.) so I created my own commitment tracking system to help me gain calm momentum and capture thoughts and actions quickly and efficiently.
It's still a work in progress, but I promise it'll only get better from here, would love any an all feedback, the good, bad, and ugly!
Big to do lists overwhelmed me, and the alternatives were costly (e.g. Omnifocus, etc.) so I created my own commitment tracking system to help me gain calm momentum and capture thoughts and actions quickly and efficiently.
It's still a work in progress, but I promise it'll only get better from here, would love any an all feedback, the good, bad, and ugly!
I got overwhelmed by large to-do lists or intimidating lists, so I created a much better, ADHD-friendly way of tracking and capturing thoughts instantly that also leverages AI to auto-sort them into a handful of common buckets.
It's essentially a commitment tracking system that's smart and adapts to you.
I use voice shortcuts to quickly capture thoughts, and it allocates them almost like a personal assistant would.
Would love open and honest feedback. I have a free and a pro tier.
I built Purgd as a lightweight iOS app for people who need to get thoughts, tasks, and mental clutter out of their head quickly.
To-do lists overwhelmed me.
It’s designed around low-friction capture: open it, dump what’s on your mind, and start turning the chaos into something manageable.
It’s not trying to be a huge productivity system. It’s more of a fast reset button for your brain.
I’d love feedback from anyone who struggles with task capture, context switching, or keeping track of what they meant to do.
I got tired of trusting coding agents based on chat history, vibes, and green tests. So I built a control system for AI-assisted work and put it on GitHub.
It's for anyone running agents that actually edit files, run commands, and call tools. The idea is borrowed from how nuclear facilities run: a control loop where nothing important gets accepted until it's verified. The flow is question, specify, execute, verify, decide, baseline, operate, learn.
Less "trust the agent," more "make it prove the important claims before you ship."
It's early and I want to know where it's wrong or overbuilt.
I got tired of trusting coding agents based on chat history, vibes, and green tests. So I built a control system for AI-assisted work and put it on GitHub.
It's for anyone running agents that actually edit files, run commands, and call tools. The idea is borrowed from how nuclear facilities run: a control loop where nothing important gets accepted until it's verified.
The flow is question, specify, execute, verify, decide, baseline, operate, learn.
Less "trust the agent," more "make it prove the important claims before you ship."
It's early and I want to know where it's wrong or overbuilt. Repo: https://github.com/FlyFission/nuclear-grade-context-engineering
What would you cut?
Recently did a pretty big overhaul. I got tired of trusting coding agents based on chat history, vibes, and green tests. So I built a control system for AI-assisted work and put it on GitHub.
It's for anyone running agents that actually edit files, run commands, and call tools. The idea is borrowed from how nuclear facilities run: a control loop where nothing important gets accepted until it's verified.
The flow is question, specify, execute, verify, decide, baseline, operate, learn.
Less "trust the agent," more "make it prove the important claims before you ship."
It's early and I want to know where it's wrong or overbuilt. Repo: https://github.com/FlyFission/nuclear-grade-context-engineering
What would you cut?
It's for anyone running agents that actually edit files, run commands, and call tools. The idea is borrowed from how nuclear facilities run: a control loop where nothing important gets accepted until it's verified. 26 skills inspired from the nuclear industry I work in. Workflows.
The flow is question, specify, execute, verify, decide, baseline, operate, learn.
Less "trust the agent," more "make it prove the important claims before you ship."
It's early and I want to know where it's wrong or overbuilt.
What would you cut?
