Can I select more than three tasks for my daily book?

No, the skill enforces a maximum of three items to encourage realistic capacity planning and prevent the 'maker' from becoming overwhelmed.

Why does the skill require a data quality check first?

Step 1 ensures that every item is correctly classified as either 'maker' or 'manager' work. This prevents organizational debt and ensures that the selection list in Step 2 is accurate.

Does this skill work with any task assignee?

The data quality check scans all assignees, but the maker selection step is specifically scoped to the user to help them plan their personal workload.

What is the main goal of the Shutdown Ritual skill?

The skill provides a structured end-of-day ceremony that ensures task data is clean and limits the user to selecting exactly three key tasks for the following day to maintain focus.

Maker Shutdown Ritual

Name: Maker Shutdown Ritual
Author: MariusWilsch

byMariusWilsch

Productivity & Workflow

Automates an evening review ceremony to ensure task data quality and prioritize the top three maker tasks for the following day.

About

The Shutdown Ritual skill facilitates a structured end-of-day workflow designed specifically for the 'maker' schedule. It ensures organizational clarity by first validating that all tasks are correctly classified as maker or manager work, then presenting a streamlined list of active items to help the user select a maximum of three tasks for their next day's physical book. By enforcing data integrity and limiting daily scope, this skill helps developers avoid overcommitment and maintain a clean project management system.

Key Features

Standardized terminal output for consistent daily reviews
Filtered view of maker-specific tasks grouped by status
Automated data quality validation for task classification
Strict 'max-3' selection logic to prevent daily burnout
Workflow enforcement requiring data cleanup before task selection
0 GitHub stars

Use Cases

Ensuring issue board data remains accurately categorized for reporting
Selecting tomorrow's focus tasks to eliminate morning decision fatigue
Closing out a development day with intentional planning

About

Key Features

Standardized terminal output for consistent daily reviews
Filtered view of maker-specific tasks grouped by status
Automated data quality validation for task classification
Strict 'max-3' selection logic to prevent daily burnout
Workflow enforcement requiring data cleanup before task selection
0 GitHub stars

Use Cases

Ensuring issue board data remains accurately categorized for reporting
Selecting tomorrow's focus tasks to eliminate morning decision fatigue
Closing out a development day with intentional planning