From waggle
Unified daily routine: ingests messages into tasks, then guides user through task refinement and dispatch. Works in both Terminal CLI and Claude Desktop. Use this skill whenever the user wants to start their day, run a morning routine, or process their daily task workflow — even if they just ask "what should I do today?". Triggers on: "daily tasks", "daily routine", "run daily tasks", "morning routine", "start my day", "what should I do today", "daily run".
npx claudepluginhub kazukinagata/waggle --plugin waggleThis skill uses the workspace's default tool permissions.
Unified daily routine that ingests messages into tasks, then guides the user through task refinement and dispatch. Works in Terminal CLI, Claude Desktop, and Cowork environments.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Unified daily routine that ingests messages into tasks, then guides the user through task refinement and dispatch. Works in Terminal CLI, Claude Desktop, and Cowork environments.
Invoke the bootstrap-session skill to establish the active provider and current user.
Skip if active_provider and current_user are already set in this conversation.
Execute the ingesting-messages skill.
If the user specified a lookback period (e.g., "past 3 days", "48 hours"), pass that instruction when invoking the skill so that ingesting-messages uses it as its lookback_period.
Record the result as intake_result. If the skill was skipped (e.g., no messaging MCP detected), set intake_result = "skipped (no messaging MCP)".
Promote the current user's Backlog tasks to Ready by filling quality gates.
current_user.
Acknowledged At exists in the schema and is null, update it to the current ISO 8601 timestamp (silent, no user prompt).refinement_result = "skipped (no Backlog tasks)" and proceed to Step 2.5.Backlog tasks to refine:
[Auto-plan N code tasks] [Quick-review M non-code tasks] [Review all one by one] [Skip]
User chooses how to proceed — no artificial threshold on count.
planning-tasks skill in pipeline mode with the task IDs. The code-planning-agent explores each codebase and generates AC/Plan. On completion, present summary: "Auto-planned N/M. K need more context."planning-tasks skill in pipeline mode. The knowledge-planning-agent proposes AC/Plan using domain templates, brainstorms with user.planning-tasks SKILL.md). Run validate-task-fields.sh for Ready before promoting.refinement_result — e.g., "3 auto-planned, 2 reviewed, 1 deferred".Review Blocked tasks and surface actionable items.
Status=Blocked AND (Assignee=current_user OR (Issuer=current_user AND Assignee empty))
Assignee includes current_user and Acknowledged At exists in the schema and is null, update it to the current ISO 8601 timestamp (silent, no user prompt).blocked_review_result = "skipped (no Blocked tasks)" and proceed to Step 3.Blocked By tasks are DoneBlocked By tasks remain non-DoneFor each unblocked task:
[DRAFT or fails semantic validation:
validate-task-fields.sh for Ready. Transition if valid.Present as a single summary table (no interactive prompts per task):
Still blocked (N tasks):
| Title | Blocked By | Blocked Days | Blocker Assignee |
| ... | ... | X days | {name} |
For tasks blocked >7 days ONLY: offer batch support options: "M tasks blocked >7 days. [Ping all blocker assignee] [Escalate all to Urgent] [Skip]"
If any task has Error Message non-empty, append to summary.
Record blocked_review_result — e.g., "2 unblocked → Ready, 3 still blocked (1 escalated)".
Execute the executing-tasks skill (normal mode).
The skill will verify all tasks have complete Execution Plans, Acceptance Criteria, and
other required fields before dispatch. The user will be prompted to fill any gaps and
choose the execution method.
Record the result as dispatch_result.
Surface stagnating Ready tasks with executor=human for action.
Status=Ready AND Executor=human AND (Assignee=current_user OR (Issuer=current_user AND Assignee empty))
Assignee includes current_user and Acknowledged At exists in the schema and is null, update it to the current ISO 8601 timestamp (silent, no user prompt).human_ready_result = "skipped (no Ready human tasks)" and proceed to Step 4.validate-task-fields.sh on each task. Note which have validation warnings (empty AC, empty Plan).Ready human tasks requiring attention:
1. [High] "Task title" (7d old) ⚠ missing AC
→ [Start now] [Fix AC/Plan] [Reassign to AI] [Delegate] [Defer to Backlog]
planning-tasks on this task (spawns appropriate planning agent).delegating-tasks skill.human_ready_result.Output the following report:
[Daily Tasks Complete]
Message Intake: {intake_result}
Task Refinement: {refinement_result}
Blocked Task Review: {blocked_review_result}
Task Dispatch: {dispatch_result}
Ready Human Tasks: {human_ready_result}
Always respond in the user's language.