Skip to content

Skill collection

These templates assume you have installed the official plugin and connected MCP. You do not need to specify tool names or detailed operations. Describe what you want done and how decisions should be made.

  1. Copy the template closest to your task.
  2. Replace the text in [brackets] with your workspace, board, and team rules. You can also paste links to boards or tasks.
  3. Send it to your connected AI. For repeat use, save it as a skill.

Ask the AI to clarify the scope if several matches exist. Have it report anything it cannot check or do. Even when you ask for “all tasks,” a result based on partial access may not represent the whole board.

Templates that change tasks include a step to review proposals before applying them. This is an instruction to the AI; the operations it can actually perform also depend on connection permissions.

What you want to do Template
Break a new initiative into tasks 1. Break down a new initiative
Extract actions from meeting notes or conversations 2. Import actions from notes
Decide what to start at the beginning of the week 3. Prioritize this week
Estimate work and record the original plan 4. Estimate sizes and record the original plan
Check overdue tasks and missing decisions before a meeting 5. Weekly task review
Investigate work that has not moved recently 6. Analyze stalled work
Summarize activity for a meeting or monthly report 7. Retrospective report
Check whether work is concentrated on a few people 8. Review workload distribution
Check whether recurring work is still useful 9. Review recurring tasks
Organize tasks that are no longer needed 10. Archive with review
Classify unlabeled tasks using agreed rules 11. Apply labels
Assign unowned tasks using team rules 12. Assign unowned tasks
Prepare incoming requests each morning 13. Triage the inbox

Create boards and lanes in the app before using these templates.

Use this when: You want to turn a new initiative into tasks.

Break this initiative into tasks we can work through in UTSUROI.
Scope: [Board name] in [Workspace name]
Initiative: [Project name]
Goal: [What we want to achieve and what finished looks like]
Steps:
1. Check the existing lanes and any tasks for the same initiative.
2. Propose parent tasks for major deliverables, with subtasks only for work we will start this week.
3. After I confirm, reuse a project with the same name if one exists; otherwise create it.
4. Create the approved tasks under that project.
Rules:
- Use at most two levels: parents and children. Later stages do not need detailed subtasks yet.
- Leave due dates and assignees undecided if they have not been agreed.
- Do not create duplicate work.
Report: List created tasks with links. Separately list anything that could not be created and explain why.

Use this when: You want to extract actions from meeting notes or conversations.

Turn the actions in these notes into UTSUROI tasks.
Scope: [Board name] in [Workspace name]
Notes:
[Paste notes here]
Steps:
1. Separate decisions, actions to take, and information shared for awareness.
2. Turn only the actions into task proposals, with one action per task.
3. Check for similar existing tasks and show me what you propose to create.
4. Create only the proposals I confirm.
Rules:
- Set assignees and due dates only when explicitly stated in the notes.
- Ask if several people share a name or a phrase such as “by next week” does not give a clear date.
- Record “Assignee undecided” or “Due date undecided” in the description when needed.
Report: Link to created tasks and explain which items were not created and why.

Use this when: You want to decide where to start the week.

Suggest the order in which I should start work this week. Do not change tasks.
Scope: [Board name] in [Workspace name]
This week: [Start date] to [End date]
Steps:
1. Check incomplete tasks that I am assigned to or hold the ball for.
2. Choose five priorities using this order as a guide:
- Overdue tasks where I hold the ball
- Tasks due this week
- Tasks where my action would unblock someone else
- Other work
3. For each, add one line explaining why it comes first and one line describing the first action.
Rules:
- Do not change due dates, lanes, or card order.
- Do not treat tasks outside the top five as unnecessary.
Report: Use a table of task, reason, first action, and link.

4. Estimate sizes and record the original plan

Section titled “4. Estimate sizes and record the original plan”

Use this when: You want to estimate work and retain its original schedule.

Propose estimates for tasks that do not have a size yet.
Scope: [Board name] in [Workspace name]
Steps:
1. Find tasks without a size.
2. Look for similar completed work on this board and use its size and reasoning as a reference.
3. For each task, show a proposed size, the reference work, and your reasoning.
4. For tasks likely to be L or XL, first propose how to split them into smaller pieces.
5. Set sizes only for proposals I confirm.
Rules:
- If no comparable work exists, say “No reference example.”
- If we also want to record original start and end dates, ask me to confirm those dates.
- Keep the current due date unchanged. Treat it separately from the original plan.
Report: Separate updated tasks from those needing a decision, with links.

Use this when: You want to check missing decisions and overdue tasks before a meeting.

Review the tasks that involve me. Do not change them.
Scope: [Board name] in [Workspace name]
Steps:
1. Check incomplete tasks that I am assigned to, hold the ball for, or created.
2. Group them into these categories:
- No ball holder
- No due date
- Overdue
- No size
3. For each task, write one line about the decision needed to move it forward.
Rules:
- Do not fill empty fields or revise due dates.
- Make it clear when the same task appears in several categories.
Report: Include counts by category, task names, questions to resolve, and links.

Use this when: You want to investigate work that has not moved recently.

Investigate incomplete tasks involving me that appear to have stopped moving.
Scope: [Board name] in [Workspace name]
Threshold: [For example, no updates in the last 14 days]
Steps:
1. Check the update history of tasks I am assigned to or hold the ball for.
2. Show the last update date and the number of days since then.
3. Read what comments and handoffs tell us, and suggest what to check next.
Rules:
- Do not conclude that actual work has stopped just because there are no updates.
- Separate confirmed facts from possible explanations.
- If you cannot check enough history, say “Unable to verify.”
- Do not change or archive tasks.
Report: Use a table of task, last update, days since update, question to resolve, and link.

Use this when: You want a summary for a regular meeting or monthly report.

Summarize activity during this period for a retrospective. Do not make changes.
Scope: [Board name] in [Workspace name]
Period: [Start date] to [End date]
Time zone for dates: Japan Standard Time
Steps:
1. Check update history during the period, including archived tasks.
2. Summarize completed work, reopened work, and work where rework is confirmed.
3. Also check incomplete tasks and their history. Separately identify those without updates during the period.
4. Give counts and up to three representative examples with links for each category.
Rules:
- A lane change alone does not prove rework.
- Distinguish a lack of recorded updates from a lack of actual work.
- Do not judge people's contribution or effort by completion counts alone.
- If you could check only part of the work, state that coverage clearly.
Report: Write a short summary ready to paste into meeting notes.

Use this when: You want to see whether work is concentrated on a few people.

Check how work is distributed and propose tasks whose ownership we could discuss.
Scope: [Board name] in [Workspace name]
Steps:
1. Summarize the incomplete tasks you can verify, separately by assignee and by ball holder.
2. Show task counts and total size, with the number of unsized tasks listed separately.
3. Suggest candidates for reassignment only from work you can confirm has not started.
Rules:
- If you cannot tell whether work has started, list it as a question instead of a candidate.
- Do not infer how busy someone is from task counts alone. Leave and other work need separate checking.
- Do not change assignments until I confirm.
- When changing assignments, preserve other assignees who are not affected and confirm who should hold the ball next.
Report: Show totals by member and links to tasks we could discuss.

Use this when: You want to check whether automatically repeated work is still useful.

Review how our recurring tasks are working. Do not change settings.
Scope: [Workspace name]
Review period: [Start date] to [End date]
Steps:
1. Check enabled recurring task configurations.
2. Check whether the tasks generated from them were completed, including archived tasks.
3. Group them into running as intended, accumulating unfinished work, and needing a review of the destination board or lane.
Rules:
- Do not guess which configuration generated a task if the relationship cannot be verified.
- Do not disable configurations or archive tasks.
Report: Show the configuration name, verified situation, reason to review it, and links to related tasks.

Use this when: You want to organize tasks that are no longer needed.

Archive tasks we no longer need, keeping them available to restore later.
Scope: [Board name] in [Workspace name]
Criteria: [For example, unstarted tasks for a launch that was canceled]
Steps:
1. Show matching candidates with reasons and links.
2. Ask whether subtasks should be included.
3. For work assigned to someone else, ask whether that person has been consulted.
4. Archive only the tasks I approve.
Rules:
- An old due date alone does not mean a task is unnecessary.
- Do not archive before I review the list.
- Do not report archived tasks as permanently deleted.
Report: Separate archived tasks from those kept, and retain links so they can be restored later.

Use this when: You want to classify unlabeled tasks using agreed rules.

Classify tasks without labels using these rules.
Scope: [Board name] in [Workspace name]
Classification rules (replace these with your team's label names):
- Bug: A feature that previously worked no longer behaves as expected.
- Improvement: It works, but is confusing, slow, or takes too many steps.
- Research: Gather information needed for a decision and reach a conclusion.
Steps:
1. Check the board's existing labels and the target tasks' contents.
2. Propose one or two matching labels for each task and show your reasoning.
3. Apply them after I confirm.
Rules:
- Keep any existing labels.
- If a needed label does not exist, ask before creating it.
- Leave uncertain tasks unclassified.
Report: Separate classified tasks from those needing a decision, with links.

Use this when: You want to assign unowned work using team rules.

Set assignees and ball holders for incomplete tasks without an assignee.
Scope: [Board name] in [Workspace name]
Assignment rules (replace these with actual names):
- Tasks labeled [Customer inquiries]: Assign [Name], who also holds the ball first.
- Work in [Project name]: Assign [Name], with [Name] holding the ball first.
Steps:
1. Check the target tasks and confirm that the named people are workspace members.
2. For tasks matching the rules, list the proposed assignee, ball holder, and reason.
3. Apply only the assignments I confirm.
Rules:
- Do not change tasks that already have assignees.
- Ask when names are ambiguous, rules overlap, or no rule applies.
- Do not choose someone else based on a guess about who seems busy.
Report: Separate assigned tasks from those needing a decision, with links.

Use this when: You want to prepare incoming requests each morning.

Organize new, unstarted tasks so they are ready to work on.
Scope: [Board name] in [Workspace name]
Intake lane: [Lane name]
Classification rules: [Which existing labels apply to which contents]
Assignment rules: [Assignees and initial ball holders for each condition]
Steps:
1. Check tasks missing any of these: labels, assignees, due date, or size.
2. Propose labels and assignees that follow the rules above.
3. Propose a due date only if it is explicit in the request. Leave size undecided if there is no reference example.
4. If the title does not describe an action, propose a rewrite.
5. Show the changes and reasons, then apply only those I confirm.
Rules:
- If a rule is left blank, ask me rather than guessing.
- Preserve existing assignees, labels, and dates.
- Leave uncertain classifications open for discussion.
Report: Separate tasks you organized from those needing human judgment, with links.

Choose a regular moment for each skill: inbox triage each morning, priorities at the start of the week, and a task review before your meeting.

Assignees are the people involved in the work. The ball holder is the person whose turn it is to act. Keep the two roles distinct when agreeing on handoff rules.

To use the same request from browser chat, save its text as a UTSUROI AI skill.

Work on [project name] in [board name].
Read relevant knowledge before starting. Afterward, save decisions, reasons and verified constraints.
Do not save transcripts or secrets. Report the link to the document you updated.
Work on [task link], then return it to me for review.
Preserve existing assignees and labels, add an AI review marker and pass the ball to me.
Leave a comment with what to check and links to the results. Do not mark it done before my review.

See the knowledge loop for details and multi-bot conventions.