Use this skill when discussing code changes, implementation work, feature status, or when starting/completing development tasks. Reminds about Linear issue tracking discipline - always having an issue in progress before writing code, marking work as done, and creating issues for unexpected scope. Triggers when users mention implementing features, writing code, or checking on work status.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear-planning-workflow:linear-disciplineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill ensures proper Linear issue tracking discipline is maintained throughout development conversations.
This skill ensures proper Linear issue tracking discipline is maintained throughout development conversations.
Apply this skill when:
Never write code without a Linear issue in "In Progress" status.
Before any implementation work:
When work is done, immediately update Linear.
A parent issue is NOT done until all sub-issues are done.
If you discover work that needs doing but has no issue, create one first.
Always: Create issue → Mark "In Progress" → Do work → Mark "Done"
"Before we begin, let's make sure there's a Linear issue for this work. Is there an existing issue we should mark 'In Progress', or should we create one?"
"Great work! Don't forget to mark the Linear issue as 'Done' to keep tracking accurate."
"This looks like new scope. Let's create a sub-issue for it before we implement it, so it's properly tracked."
Todo → In Progress → Done
↓
(If blocked)
↓
Blocked → In Progress → Done
When using Claude Code's built-in plan mode, Linear tracking happens automatically:
linear-plan-mode asks if plan should be tracked in Linear| Tool | Purpose |
|---|---|
linear-mvp-project-creator | Creates parent issue + sub-issues from plan |
linear-project-context | Checks for existing feature issues |
linear-plan-sync | Syncs plan file changes to Linear |
For detailed plan mode workflow, see the linear-plan-mode skill.
This discipline integrates with:
/planFeature - Creates properly structured issues/work-on-feature - Enforces status tracking during executionexecute-issue agent - Automatically manages status transitionslinear-plan-mode skill - Maintains plans in Linear during plan modeRemember: Linear is the source of truth. Keep it accurate.
npx claudepluginhub jclfocused/claude-agents --plugin linear-planning-workflowExecutes code tasks from Linear sub-issues: resolves dependencies, implements changes, validates Done Criteria, and syncs status. Use when asked to work on a Linear issue (e.g. PRI-42).
Creates structured Linear tickets for project planning, feature breakdowns, and bug fixes. Uses Linear as an agent control plane with complete work briefs, status tracking, and dependency management.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.