plan-work

Generates a prioritized daily work plan from Linear tickets, Notion PRDs, and GitHub repo state.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill plan-work-amakaflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/Amakaflow/amakaflow-dev-workspace/tree/main/.claude/skills/plan-work
Command: npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill plan-work-amakaflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding what to work on each day requires manually checking Linear tickets, Notion PRDs, and open GitHub PRs across many repositories, which is slow and error-prone. This Skill aggregates all three sources and produces a prioritized daily work plan with clear task routing between team members. ## Core Features & Use Cases - Multi-source data gathering: Pulls active issues from Linear, PRD readiness from Notion, and open PRs plus recent commits from GitHub in parallel. - Priority and routing analysis: Identifies critical-path blockers, flags stuck or stale items, and routes tasks to David (Claude Code) or Joshua (Antfarm) based on PRD readiness, repo scope, and risk. - Structured daily digest: Outputs a scannable report covering critical path, each person's queue, PRs needing attention, stale items, workspace health, and recently completed work. - Use Case: At the start of your work day, invoke the Skill to get a two-minute digest showing which AMA tickets are unblocked, which have PRDs ready for Joshua, and which PRs have failing CI. ## Quick Start Ask the assistant to run the plan-work skill and generate today's prioritized work plan from Linear, Notion, and GitHub.

Frequently Asked Questions about plan-work

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

FAQPage Schema
How do I generate a daily work plan from Linear and GitHub?

Invoke the plan-work skill at the start of your day. It queries Linear for backlog, in-progress, and review issues, checks Notion for PRD readiness, and lists open GitHub PRs, then outputs a prioritized digest with task routing recommendations.

How does the skill decide which tasks go to the AI coding agent?

Tasks route to Joshua (Antfarm) only when they have a detailed PRD, are scoped to a single repository, follow existing patterns, and require no architectural or UX decisions. Anything involving architecture, multi-repo work, CI/CD, or spec writing routes to David.

What integrations does the plan-work skill require?

It requires the Linear MCP plugin, the Notion MCP integration, and an authenticated GitHub CLI (gh). The skill runs a health check on all three sources first and proceeds with available sources if any fail.

Can the skill automatically assign or update Linear tickets?

No. The skill produces recommendations only and never auto-assigns tickets, moves issue states, or creates new tickets. David has final approval on all task assignments.

Why are some open PRs not flagged in the daily digest?

Joshua's PRs are reviewed by CI and GitHub Actions, so they are omitted unless CI is failing. The digest only surfaces PRs with failing CI, PRs authored by David needing attention, or stale PRs open over five days with no activity.