OscoContext-rich tasks
Every task arrives with the context to finish it.
A two-line ticket turns into a meeting. In Osco, a task holds the reason for the work, a checklist of what done means, what it is blocked by, and links to the docs, endpoints and code involved.
The problem
What gets in the way today
- Handoffs need a call because the ticket does not explain itself.
- "Done" means different things to the author and the reviewer.
- Work starts before the task it depends on is finished.
How Osco helps
Context that travels with the work
The why, written down
Every task has a place for the reason, so trade-offs can be made without asking.
Acceptance criteria that gate done
A task can only be marked done when every criterion is checked.
Dependencies that block
Mark what a task is blocked by, and Osco stops it closing before its blockers are done.
Notified at the right time
Assignees, reviewers and authors are notified about assignments, reviews, comments and completion.
How it works
From setup to everyday use
- 1
Describe
Write what needs to change and why.
- 2
Define done
Add acceptance criteria as a checklist.
- 3
Link
Attach docs, endpoints, features and blocking tasks.
- 4
Hand off
Assign an owner and a reviewer. They get notified and can start right away.
Frequently asked questions
Can a task be closed with unchecked criteria?
No. All acceptance criteria must be checked before a task can be marked done.
Who gets notified?
The assignee when assigned, the reviewer when asked to review, and the author, assignee and reviewer on comments and completion. You are never notified of your own actions.
Can tasks link across projects?
Tasks link to docs, endpoints and features, and docs can link to docs in other projects in the same workspace.
More use cases
Give every task the context to finish it.
Start free with your team. Bring your Markdown, connect your coding agents and invite people when you are ready.