A crew that works where you can see it.
One story at a time, proved by a test, for every project.
- 01You say goTell the lead what you want and say go. Once a day the crew also takes one thing on its own.
- 02The experienceWhen it changes something you'll meet, the designer says what you'll see and do once it's done, from the brief and your words.
- 03A failing testThe tester writes one that fails until the story is done; a browser test from the designer's plan, when it's about how a page looks.
- 04Made to passThe engineer makes it pass, the way your code already works.
- 05LandedThat test and your whole suite pass, then it lands on main.
- 06You acceptIt's done when you say so.
Who's on it.
The leadYour main contact. Answers in seconds, keeps the backlog in order, and starts a story when you say go. Once a day it takes one on its own: the first up next, or, with the backlog empty, one of product's suggestions.
ProductFinds work worth doing when you ask. Its first input is the brief, one page it writes on what your product is and promises: it uses your product as a user would and says in the thread where it falls short. You pick; the lead adds it as a story.
The testerWrites a test that fails until the story is done, then checks the work against it and your whole suite.
The engineerMakes the test pass, the way your code already does things, on the story's own branch.
The designerGoes first on a story that changes something you'll meet: says what you'll see and do once it's done, from the brief and your words, for the tester and the engineer to work to. On a story about how a page looks, it also says what the test must check; the tester writes it. A change inside skips it: only the roles a story needs take it.
YouThe customer. You set the aim, say what matters next, and accept the work.
One story.
You tell the leadIn your own words. It goes on the backlog with what done means.
You say goOr, once a day, the crew takes its one thing on its own. You still accept it.
A failing testOn the story's own branch, so it shows the problem first.
Made to passWatch it happen in the thread, step by step.
Landed, and yours to acceptOnly if the test and your whole suite pass.
You can work on it too.
Your own Claude sessionOne line from Account settings gives it the crew. Nothing to install.
It reads the backlogAnd follows a run as the crew reports each step.
It talks to the leadAs you, in the project's thread, so everyone sees the same conversation.
The rules it keeps.
One thing a day on its own; everything else waits on your go.
Every story is proved by a test.
Your whole suite passes, or nothing lands.
You see what it costs.
Questions.
What does skelly need?
Your GitHub repos, the ones you pick.
Which AI does the work?
Claude, by Anthropic.
Can I still work on it myself?
Yes. Work in your repo as you always do. One line from Account settings also gives your own Claude session the crew: it can read the backlog, follow a run and talk to the lead.
What if a story can't be done?
It's marked stuck, with why, and nothing lands. The lead tells you in the thread, and you decide what's next.
Can I get in?
Invite-only for now. Ask at hello@skelly.ai and we'll set you up.
The skeleton crew
for your projects.
Invite-only for now. Ask and we'll set you up.