ArcturusDC STEa — Plan • Build • Test
Idea → prompt → backlog → test → learn — single system.
Start new thread

ArcturusDC STEa — Plan • Build • Test - Idea → prompt → backlog → test → learn — single system.

by•
STEa keeps planning, delivery, testing, and documentation in sync. Harls is a Miro-style board for discovery, Filo a Trello-meets-Jira board for builds, Hans turns acceptance criteria into test cases, and Ruby keeps living docs in one place. Everything links — move work seamlessly through each stage. Add AutoProduct to turn a brief or a prompt from within an LLM into a complete, testable backlog of Epics, Features and Cards (stories).

Add a comment

Replies

Best
Maker
📌
I built STEa because every time I hit a sticking point building my own apps, I ended up building a tool to fix it. Planning was messy → Harls. Delivery needed structure → Filo. Testing was a headache → Hans. Docs kept getting lost → Ruby. It’s basically all the bits I wish I’d had when I started — less admin, less duplication, less heavy lifting, so I could just get back to building.

 Curious, does it integrate all these tools in one dashboard?

Maker

 Fair question, currently it will depend on the stage of build you are on. For example in build stage/phase your dashboard is Filo (backlog/progress etc). In testing the primary dashboard is Hans showing how many tests run and success failure rates. Interesting idea though perhaps...a unified dashboard across Prod+Eng? Perhaps on the Home page for STEa.

Maker

 something like this?