Use this skill when discussing code changes, implementation work, feature status, or when starting/completing development tasks. Reminds about Jira issue tracking discipline - always having an issue in progress before writing code, transitioning to done, and creating Subtasks for unexpected scope. Triggers when users mention implementing features, writing code, or checking on work status.
/plugin marketplace add jclfocused/claude-agents/plugin install jira-planning-workflow@laserfocused-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples.mdreferences.mdThis skill ensures proper Jira issue tracking discipline is maintained throughout development conversations.
Apply this skill when:
Never write code without a Jira issue in "In Progress" status.
Before any implementation work:
When work is done, immediately transition in Jira.
A Story is NOT done until all Subtasks are done.
If you discover work that needs doing but has no issue, create a Subtask first.
Always: Create Subtask → Transition "In Progress" → Do work → Transition "Done"
Unlike Linear where you set status directly, Jira uses transitions:
To Do → In Progress → Done
↓
(If blocked)
↓
Blocked → In Progress → Done
Use mcp__mcp-atlassian__jira_get_transitions to see available transitions, then mcp__mcp-atlassian__jira_transition_issue to execute them.
"Before we begin, let's make sure there's a Jira issue for this work. Is there an existing issue we should transition to 'In Progress', or should we create a Subtask?"
"Great work! Don't forget to transition the Jira issue to 'Done' to keep tracking accurate."
"This looks like new scope. Let's create a Subtask for it before we implement it."
This discipline integrates with:
/planFeature - Creates properly structured Stories with Subtasks/work-on-feature - Enforces status tracking during executionexecute-issue-jira agent - Automatically manages transitionsRemember: Jira is the source of truth. Keep it accurate.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.