tasks

Aggregate tasks from Slack, Linear, Monday, and notes into a daily Kill List and Parking Lot.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/namankumar/product-os --skill tasks-namankumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tasks
Source: https://github.com/namankumar/product-os/tree/main/.claude/skills/tasks
Command: npx skills add https://github.com/namankumar/product-os --skill tasks-namankumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize scattered tasks into a concise daily Kill List and Parking Lot backlog.

Core Features & Use Cases

  • Surface urgent items, blockers, and dependencies from multiple sources to keep you aligned with milestones.
  • Generate a focused Kill List for today plus a Parking Lot for everything else, improving clarity and throughput.
  • Works with cached data from Slack, Linear, Monday, notes, and docs to maintain context and reduce context-switching.

Quick Start

Provide or confirm your current task sources and run the skill to generate today’s Kill List.

Frequently Asked Questions about tasks

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

FAQPage Schema
What is a Kill List and Parking Lot for task workflow planning?

Organizing scattered tasks into a daily Kill List and Parking Lot surfaces urgent blockers and quick batch tasks. This workflow planning method improves clarity by aggregating items from Slack, Linear, Monday, and notes.

How do I organize scattered tasks from Slack and Linear into a daily prioritized list?

To organize scattered tasks from Slack, Linear, and Monday, run the skill to aggregate cached data into a daily Kill List. It applies prioritization rules to surface urgent blockers, dependencies, and quick batch tasks.

Can I synchronize my task prioritization with project cadence using cached data?

Yes, task prioritization is synchronized with project cadence using persistent state via cache updates. The skill aggregates cached data from Slack, Linear, Monday, notes, and docs to maintain context across your workflow.

How does task aggregation handle blockers and dependencies from multiple sources?

Task aggregation surfaces urgent blockers, waiting-on work, and dependencies by pulling cached data from Slack, Linear, and Monday. It enforces prioritization rules to keep your daily Kill List aligned with milestones.

What is the best way to maintain context and reduce context-switching across task sources?

Aggregating cached data from Slack, Linear, Monday, notes, and docs into a single focused Kill List reduces context-switching. This maintains context and aligns your workflow with project milestones and dependencies.