shutdown-ritual

Validate issue classifications and select up to three maker tasks by status.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MariusWilsch/clarity-workflow-plugin --skill shutdown-ritual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shutdown-ritual
Source: https://github.com/MariusWilsch/clarity-workflow-plugin/tree/main/skills/shutdown-ritual
Command: npx skills add https://github.com/MariusWilsch/clarity-workflow-plugin --skill shutdown-ritual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the end-of-day process by ensuring data quality and facilitating the selection of key tasks for the next day's work.

Core Features & Use Cases

  • Data Quality Check: Automatically identifies tasks missing essential 'maker' or 'manager' classifications.
  • Maker Task Selection: Presents tasks assigned to MariusWilsch, categorized by status (Review, In-Progress, To-Do), allowing for the selection of up to three tasks for the physical work journal.
  • Use Case: At the end of the workday, run this ritual to quickly verify that all your project tasks are properly categorized and then select the top 3 most important tasks to focus on tomorrow.

Quick Start

Run the shutdown ritual to check data quality and select your top three tasks for tomorrow.

Frequently Asked Questions about shutdown-ritual

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate an end of day task selection and prioritization process?

An end of day task selection ritual automates prioritization by validating maker/manager classifications on issues, then displaying maker-specific tasks grouped by status for you to select up to three tasks for tomorrow's work journal.

How does data validation work for developer productivity task management?

Data validation for task management works by running a script that checks project issues for missing maker or manager classifications, ensuring all tasks are properly categorized before you begin selecting your priorities for the next day.

What is the best way to group maker tasks by status for daily work journals?

Grouping maker tasks by status is best handled by executing a script that displays tasks categorized by Review, In-Progress, and To-Do statuses, allowing you to select a maximum of three tasks for your physical work journal.

Can I limit my task selection to exactly three tasks for the following day?

Yes, you can limit task selection to three tasks. The maker task selection process presents your categorized tasks and enforces a maximum of three selections to ensure strict prioritization for the following day's work.

Why do I need maker and manager classifications for end of day workflow validation?

Maker and manager classifications are needed because the workflow validation checks for these missing classifications on issues to ensure data quality and task clarity before you execute the task selection ceremony.

What are the limitations of using a shutdown ritual for task management?

A limitation of this shutdown ritual is that it specifically filters for tasks assigned to the MariusWilsch account and requires issues to have predefined maker or manager classifications to function correctly.