Issue triage and decision log
New issues, launch discussions, and decisions organized for review.
weekly-issue-triage.mdweekly-product-decision-log.mdWeekly team operationsStart Monday with every update
Start Monday with every update
collected and ready to review.
Connect the tools where work already happens. Commander coordinates the weekly window, specialists turn raw updates into an operational status, and consequential posts or updates stay visible for owner review.
- Start with
- Connected work sources, a weekly cadence, and clear owner review boundaries
- Finish with
- A triage, decision log, team update, follow-up tracker, and permission review
A recurring Commander run prepares Monday’s project notes, owner follow-up tracker, and weekly team update for human review.
Follow along
Prepare the weekly team update
Copy it, paste it into the Orkas input box, and start trying it.
Example request
Every Monday, summarize new launch issues and decisions from the connected workspace, compare them with the plan, prepare the team status and owner follow-ups, and leave any external post or assignment ready for my review before it is sent.
What you receive
The operating package the team needs before the first stand-up
Recurring collection and drafting happen on cadence; consequential external actions stay visible for owner review.
Team status and follow-ups
A readable weekly update with owner assignments and open follow-ups.
weekly-team-status-update.mdowner-follow-up-tracker.csvPermission review
A record of connector access and consequential actions that require review.
connector-action-permission-review.mdDetailed process
Connect the sources, define the routine, review external actions, run it on cadence
Connect work sources
Authorize only the GitHub, Notion, Slack, mail, or calendar sources the routine needs.
Describe the routine
Set the weekly window, expected files, owners, and exception rules.
Review external actions
Check drafts and connector access; individual confirmation is not guaranteed for every send.
Run on cadence
Reuse the same operating workflow each week without rebuilding it.
Start this work
Download Orkas — freeTry this use case in Orkas
Free, open source, and runs on your machine.
FAQ
Weekly operations questions
Common answers about connectors, recurring runs, and owner review.
Which tools can Orkas connect to?
Orkas connects to GitHub, Notion, Slack, Gmail, and Google Workspace — Google Calendar, Google Docs, Google Sheets, and Google Tasks — over OAuth. You connect a service, and your agents discover and call the actions that connector exposes. Actions are limited to what each connector's OAuth integration offers, and every connector is opt-in per service.
Can it run recurring automations?
Yes. You direct the agent team by chat across your connected tools — draft and send email, triage your inbox, post to Slack, create or update Notion pages, open or triage GitHub issues, manage calendar events and tasks, or compile a weekly report from several sources — and you can run that work on a recurring basis.
Is connecting my accounts safe?
Connections use OAuth, connector tokens are stored encrypted on your machine, and each connector is opt-in. Connector actions are tool calls and are not guaranteed to pause for a separate approval prompt, so review access before external actions. Use Orkas-managed official models, or connect your own provider; own-provider model calls go direct. Optional sync stores the data you choose to sync on Orkas servers, and the free edition sends limited usage metadata, not your content.
Is Orkas an AI workflow automation tool?
Yes. Orkas turns repeatable work into reusable sub-agents and skills you can summon by chat. It is best for workflows that need reading, reasoning, tool calls, approvals, and follow-up across files, code, or connected workspace apps. For the broader positioning, read AI Workflow Automation with Orkas.
Ready when you are
Put a team on your workspace
Free, open source, and runs on your machine.