name	edge-ic:weekly-wrapup
description	End-of-week automation - review active work and prepare next week's TODO
allowed-tools	["Read","Write","mcp__atlassian__jira_search","mcp__atlassian__jira_add_comment","mcp__atlassian__jira_transition_issue","AskUserQuestion"]
user-invocable	true

IC: Weekly Wrap-up

Perform end-of-week workflow automation: review active Jira tickets, add status updates, and prepare TODO file for next week.

Task

Automate the weekly wrap-up process by reviewing active work, gathering status updates, and creating a structured TODO file for the upcoming week with carry-over items and suggested priorities.

Instructions

Parse arguments: --dry-run, --no-jira, --no-todo
Query active Jira tickets: assignee = currentUser() AND statusCategory IN ("In Progress", "To Do")
Group tickets by status: Code Review, POST, In Progress, ASSIGNED, To Do
Prompt for status updates for each ticket
Read current week's TODO files: Resolve Monday's date from current week and read $HOME/.daily/YYYY/MM/YYYY-MM-DD.md. File must conform to format defined in plugins/edge-ic/references/TODO_FILE_FORMAT.md. If validation fails in --dry-run mode, display errors but continue; otherwise abort.
Generate next Monday's TODO file: Resolve next Monday's date and write to $HOME/.daily/YYYY/MM/YYYY-MM-DD.md. Generated file must pass validation against plugins/edge-ic/references/TODO_FILE_FORMAT.md before writing. If validation fails in --dry-run mode, display errors but continue; otherwise abort.
Generate backlog suggestions
Display summary

Important

Interactive by default - User must confirm each status update
Use currentUser() in JQL
Preserve context in carry-over items, including all indented link sub-lines beneath them
Support --dry-run to preview before committing

TODO File Format and Validation

TODO files are stored at $HOME/.daily/YYYY/MM/YYYY-MM-DD.md
Files must conform to format defined in plugins/edge-ic/references/TODO_FILE_FORMAT.md
Validation is enforced for both read and write operations
Validation failures abort the operation (except in --dry-run mode, which displays errors and continues)
User-invocable skill - only invoke when the user explicitly requests weekly wrap-up automation

Más de este repositorio

mismo repositorio

edge-ic-morning

openshift-eng/edge-tooling

Surface your daily task list — QA-ready tickets, sprint backlog, carry-over items, open PRs, RHEL verification queue, and quarterly reminders. Use at the start of your day to see what needs attention.

2026-07-097

edge-ic-task-info

openshift-eng/edge-tooling

Show detailed info about a specific TODO task — its tracked links, notes, and live Jira/PR status. Use when the user asks about a task, wants context to resume work on it, or asks what's needed to finish a ticket. Not for listing all tasks (read the TODO file directly or use edge-ic:sprint-status for sprint-wide views)

2026-07-097

microshift-release-automated-testing

openshift-eng/edge-tooling

Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts

2026-07-097

microshift-ci-job-pcp-dashboard

openshift-eng/edge-tooling

Generate interactive PCP performance dashboard from a Prow job URL

2026-07-027

lvms-ci-prow-job

openshift-eng/edge-tooling

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

2026-06-307

microshift-ci-prow-job

openshift-eng/edge-tooling

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

2026-06-307

IC: Weekly Wrap-up

Perform end-of-week workflow automation: review active Jira tickets, add status updates, and prepare TODO file for next week.

Task

Automate the weekly wrap-up process by reviewing active work, gathering status updates, and creating a structured TODO file for the upcoming week with carry-over items and suggested priorities.

Instructions

Parse arguments: --dry-run, --no-jira, --no-todo

Query active Jira tickets: assignee = currentUser() AND statusCategory IN ("In Progress", "To Do")

Group tickets by status: Code Review, POST, In Progress, ASSIGNED, To Do

Prompt for status updates for each ticket

Read current week's TODO files: Resolve Monday's date from current week and read $HOME/.daily/YYYY/MM/YYYY-MM-DD.md. File must conform to format defined in plugins/edge-ic/references/TODO_FILE_FORMAT.md. If validation fails in --dry-run mode, display errors but continue; otherwise abort.

Generate next Monday's TODO file: Resolve next Monday's date and write to $HOME/.daily/YYYY/MM/YYYY-MM-DD.md. Generated file must pass validation against plugins/edge-ic/references/TODO_FILE_FORMAT.md before writing. If validation fails in --dry-run mode, display errors but continue; otherwise abort.

Generate backlog suggestions

Display summary

Important

Interactive by default - User must confirm each status update

Use currentUser() in JQL

Preserve context in carry-over items, including all indented link sub-lines beneath them

Support --dry-run to preview before committing

TODO File Format and Validation

TODO files are stored at $HOME/.daily/YYYY/MM/YYYY-MM-DD.md

Files must conform to format defined in plugins/edge-ic/references/TODO_FILE_FORMAT.md

Validation is enforced for both read and write operations

Validation failures abort the operation (except in --dry-run mode, which displays errors and continues)

User-invocable skill - only invoke when the user explicitly requests weekly wrap-up automation