From linear-pack
Issue lifecycle management with Linear: create, update, and transition issues. Use when implementing issue CRUD operations, state transitions, or building issue management features. Trigger with phrases like "linear issue workflow", "linear issue lifecycle", "create linear issues", "update linear issue", "linear state transition".
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear-pack:linear-core-workflow-aThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Master issue lifecycle management: creating, updating, transitioning, and organizing issues.
Master issue lifecycle management: creating, updating, transitioning, and organizing issues.
For full implementation details and code examples, load:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
Issue not found | Invalid ID or identifier | Verify issue exists |
State not found | Team workflow mismatch | List states for correct team |
Validation error | Invalid field value | Check field constraints |
Circular dependency | Self-blocking issue | Validate relationships |
Continue to linear-core-workflow-b for project and cycle management.
Basic usage: Apply linear core workflow a to a standard project setup with default configuration options.
Advanced scenario: Customize linear core workflow a for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub p/ktiseos-nyx-linear-pack-plugins-saas-packs-linear-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.