Brief to plan
- Paste or upload a messy launch brief.
- Keel returns a plan preview with epics, tasks, estimates, and dependencies.
- Edit, remove, or accept items. Loops and missing owners are flagged.
- Approve, and the tasks and graph are created.
- Keel
- How it works
A signal comes in. Only you change the plan.
Every flow in Keel follows one loop: a signal becomes a risk, a risk becomes a proposal, and only an approval changes the plan. Here is each step, and who does what.
The loop
Agents can read and propose freely. Execution happens only after the approval step, and it always writes an audit record.
- Signal
A chat message, commit, or meeting moment that may change the plan.
- Risk
Keel links the signal to a task and computes every downstream date.
- Proposal
A change with reasoning, confidence, and evidence, waiting for review.
- Your approval
Approve, edit, or reject. Your workspace setting decides what needs this.
- Record
One audit event names the agent, the approver, and the evidence.
The model explains. Code does the maths.
The AI reads and writes words. Dates, the critical path, and risk scores come from graph algorithms, so they can be checked and repeated.
| Feature | The model | Keel's code |
|---|---|---|
| Brief to plan | Turns the brief into epics, tasks, estimates, and dependencies | Checks the structure, rejects loops, and schedules dates |
| Blockers | Spots messages like “blocked” or “delayed” and links them to a task | Walks the graph to find dependents and recompute dates |
| Drift | Explains the mismatch in words | Applies rules: no commits in N days, status against activity, overdue |
| Meetings | Pulls out decisions, actions, owners, and due dates | Matches owners to people, resolves dates, removes duplicates |
| Weekly summary | Writes the story from the numbers it is given | Computes every metric and trend |
| Ask Keel | Answers from retrieved passages only | Finds passages you are allowed to see |
Four flows, one loop
Delay to downstream risk
- Someone writes “Backend auth is delayed 4 days” in project chat.
- Keel links it to Auth service and computes every dependent task's new date.
- Those tasks are marked at risk, and launch health changes.
- A grouped proposal appears, “Shift 3 tasks +4 days”, with the message as evidence.
Meeting to actions
- Upload the audio or transcript of a project meeting.
- Keel extracts decisions, action items, owners, and dates, each linked to its moment.
- New tasks arrive as proposals; decisions join the log after review.
Ask Keel
- Open the command palette and ask, “What's the biggest risk this week?”
- Keel answers with citations from what you can access, or says it lacks evidence.
Integrations feed the record, never the plan
Connected tools send events to Keel. They cannot change tasks directly; anything they suggest goes through a proposal.
| Tool | What Keel does with it | When |
|---|---|---|
| GitHub | Links commits, pull requests, and reviews to tasks by branch name or task ID. A merged PR proposes moving the task on. | At launch |
| Meeting transcription | Turns audio into a timestamped transcript with speakers. | At launch |
| Google Calendar | Attaches meetings to projects and reminds you of deadlines. | Next |
| Slack | Reads chosen channels for blockers and lets you approve proposals from Slack. | Later |
| Forwarded emails become signals on a project. | Later |
Try the loop on a real launch
Start with GitHub and one project. You will see your first proposal the next time a delay is mentioned.