All activity
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).
ArcturusDC STEa — Plan • Build • TestIdea → prompt → backlog → test → learn — single system.
David Loakeleft a comment
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.
ArcturusDC STEa — Plan • Build • TestIdea → prompt → backlog → test → learn — single system.