jackhutson

Use when needing to understand a Jira ticket before acting on it — pulling context for an agent, reviewing a ticket's full picture, loading ticket details for decision-making, or when asked to "show me" or "what's in" a ticket.

Use when the user has a spec, architecture doc, implementation plan, or feature description and wants to break it into Jira tickets for distribution to people or agents. Also triggered by "create tickets from this plan" or "file tickets for this spec".

Use when work on a ticket has reached a stage boundary — started working, sent for review, completed, blocked, or reopened. Handles status transition, comment, and field updates in one pass.

Use when the user mentions Jira, issues, tickets, sprints, work items, or any project management task involving Atlassian. Routes to workflow skills or delegates to jira-agent subagent.

Use when the user assigns a ticket to the agent, says "work on this ticket", "pick up this item", or wants the agent to claim a ticket and execute against it. Procedural harness that wraps any work with Jira discipline.

Use when a project's workflow statuses need to be configured for the first time, or refreshed. Triggered automatically by jira-progress when a project is missing from config/workflows.json, or manually via "configure workflow", "set up statuses for X", "refresh workflow for X".

This skill should be used when the user asks to "refresh Todoist", "sync Todoist", "list my projects", "show my labels", "update Todoist structure", "show my Todoist sections", or when a todoist-agent operation fails with a not-found error for a project, label, or section name. Fetches and caches Todoist structure for name-to-ID resolution.

This skill should be used when the user asks to "add a task", "create a Todoist task", "complete a task", "mark task as done", "update a task", "delete a task", "show my tasks", "what's due today", "list my Todoist tasks", "check my to-dos", "what do I need to do", or mentions Todoist task management, to-do items, or task queries by project, priority, label, or due date. Delegates all operations to the todoist-agent subagent.

Use when a project's workflow statuses need to be configured for the first time, or refreshed. Triggered automatically by jira-progress when a project is missing from config/workflows.json, or manually via "configure workflow", "set up statuses for X", "refresh workflow for X".

Use when needing to understand a Jira ticket before acting on it — pulling context for an agent, reviewing a ticket's full picture, loading ticket details for decision-making, or when asked to "show me" or "what's in" a ticket.

Use when the user assigns a ticket to the agent, says "work on this ticket", "pick up this item", or wants the agent to claim a ticket and execute against it. Procedural harness that wraps any work with Jira discipline.

Use when the user has a spec, architecture doc, implementation plan, or feature description and wants to break it into Jira tickets for distribution to people or agents. Also triggered by "create tickets from this plan" or "file tickets for this spec".

Use when work on a ticket has reached a stage boundary — started working, sent for review, completed, blocked, or reopened. Handles status transition, comment, and field updates in one pass.

Use when the user mentions Jira, issues, tickets, sprints, work items, or any project management task involving Atlassian. Routes to workflow skills or delegates to jira-agent subagent.

Use acli jira CLI for Jira work item management, project operations, sprint tracking, and board management with JQL search capabilities. Load this skill for ad-hoc Jira operations not covered by workflow skills, or when you need detailed ACLI command reference.

This skill should be used when the user asks to "start my day", "run my daily ritual", "plan my day", "morning review", or "walk me through my todos". Morning walkthrough: triage overdue, capture what's on your mind, prioritize, sort, and print today's plan.

This skill should be used when the user asks to "triage my inbox", "process my Todoist inbox", "get to inbox zero", "clean up my tasks", or when /todoist:daily hands off inbox processing. Clarifies and files each inbox item, applying all changes as one confirmed batch.

This skill should be used when the user says "capture that", "add those to my todo list", "file the follow-ups from this session", "turn these loose ends into tasks", or at the end of a work session with deferred items. Harvests follow-ups from the current conversation and diff into Todoist tasks in one confirmed batch.

This skill should be used when the user asks to "set up Todoist", "install td", "connect Todoist", "authenticate Todoist", when any td command fails because the CLI is missing or unauthenticated, or when migrating from the v1 MCP-based version of this plugin. Bootstraps the official td CLI: install, OAuth login, health check, and an optional permission allowlist.

This skill should be used when the user asks to "add a task", "create a Todoist task", "complete a task", "update a task", "delete a task", "show my tasks", "what's due today", "check my to-dos", "list my projects/labels/filters", or mentions Todoist task management, task queries by project, priority, label, or due date. Runs the official td CLI directly; delegates account-sized reads to todoist-agent.