Been dogfooding something we built called Skene. Its basically a workflow that stays inside Cursor instead of bouncing to a seperate dashboard for “what should we build next.”
The Cursor plugin exposes six commands: /skene-init, /skene-analyze, /skene-plan, /skene-build, /skene-deploy, /skene-status. Init sets up .skene.config (pick a provider, drop in a key). Analyze runs against the repo and writes structured output under .skene/analysis/.
Plan gives you prioritized growth features to implement with scores and complexity. Build generates an implementation prompt that points at real paths and patterns, not generic advice. Deploy is where Supabase shows up if the loop needs it: migrations land under supabase/migrations/, dry run first. Status checks whether the active loop is actually reflected in code, tests, telemetry.
There are also hooks that run in the background. After edits it runs a quiet status pass so you dont have to remember to check progress manually. Before shell stuff it sanity checks prerequisites so you get fewer cryptic failures.
Happy to answer questions about the plugin or the CLI.