Beta
Korey writes the spec your coding agents build from.
Coding agents made building cheap. Now the spec is what slows you down. Korey turns an idea, a chat or an existing Epic into a spec, writes the tasks into Shortcut, Jira or GitHub Issues, and hands them to the coding agents you already use. Korey reads the spec every time it executes work.
Why the spec is the bottleneck now
Agents write code in minutes, but they build exactly what they are told. The decisions that change a plan land in PR comments, Slack threads and quickly added tasks, and never make it back to the spec. Every teammate and every agent ends up working from a different version of the plan.
In Korey, the spec, the chats about it and the tasks built from it live in one Project, and Korey reads the spec every time it executes work.
How Korey writes and uses the spec
- Start from an idea, a chat or an Epic. Ask Korey to spec out an idea in any chat, turn an existing chat into a Project, or create a Project from an Epic and bring its Stories or Issues with it.
- Edit the spec directly or in chat. The Spec is a freeform document. When the scope changes, edit it yourself or ask Korey to update it.
- See the work next to the spec. The Execute column lists the Project's Stories and Sub-tasks, grouped by state.
- Assign tasks to coding agents. Pick Claude Code, Codex or Devin from the task card, and watch the task's status change as the agent works.
Works with your tracker, your agents and Slack
Your tracker stays the system of record
Work created in a Project lands in Shortcut, Jira or GitHub Issues as real tasks, and statuses stay in sync.
Your agents build from the same spec
Korey references the Spec when it executes work, so each agent task starts from the current plan.
Your team follows along in Slack
Link a Slack channel to the Project so anyone with a Korey account can ask Korey for its status. Share the Project permalink with everyone else.
Frequently asked questions
What is an AI spec generator?
A tool that turns a rough description of work, such as an idea, a Slack thread or an existing Epic, into a structured spec that people and coding agents can build from. Korey writes the first draft, breaks it into tasks, and updates the spec when you ask it to in the Project chat.
Can Korey write a spec from an Epic I already have?
Yes. Create a Project from an existing Epic and Korey brings its Stories or Issues in with it, or ask Korey in the Project chat to build the Spec and import the work.
Which coding agents can build from the spec?
Assign Stories and Sub-tasks to agents such as Claude Code, Codex or Devin straight from the task card, or tell Korey in chat which tasks to pick up. Korey references the Spec when it executes work, and progress updates live as agents finish.
How does the spec stay up to date?
The Spec is an editable document inside the Project. Change it directly, or ask Korey in the Project chat to update it when scope or direction changes. Chats started in a linked Slack channel show up in the Project and add to its context.
Who can edit the spec?
Anyone in your Korey organization can open the Project, read the Spec and start a chat in it. For now, only the Project owner edits the Spec directly and assigns work from the Execute column.
Is my data safe with Korey?
Korey is SOC 2 Type II compliant, runs under a Zero Data Retention agreement with Anthropic, and never trains on your data.
Can I try it for free?
Yes. Every team starts with 100 free interactions, no credit card required.
Write your first spec
Open Korey and ask it to spec out an idea, or start from an Epic you already have.