9 skills · sorted by relevance
Turn contracts, reports, and scanned forms into cited facts and proposed tasks. Preserve deadlines, explicit owners, source locations, and uncertainty, then create and verify records in an external tracker only within the user's approved scope.
Turn meeting notes or transcripts into sourced decisions and action items with owners and deadlines. Check existing tasks for duplicates, then draft minutes, tickets, and follow-up messages while keeping missing details and unresolved conflicts visible.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Review existing tests and CI, the automated checks run during development, for redundant coverage, misplaced tests, and opportunities to reduce runtime or cost. Receive file-specific recommendations based on documented improvement patterns, with uncertain findings separated.
Work through your assigned tasks from Circleback meetings, using meeting notes to clarify each request. Make code changes, create tickets, or draft replies, then update task status only when the underlying work is actually finished.
Turn meeting notes into an accountable register — extract decisions, actions and open questions, flag ownerless items, track follow-through. Use when commitments get dropped or a recurring meeting decides nothing.
The English summary is being prepared. Showing the original description.
Prepare structured briefings for meetings with legal relevance and track action items. Use when prepping legal meetings.
The English summary is being prepared. Showing the original description.
Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.
The English summary is being prepared. Showing the original description.
Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.