Route Linear tracking work through a methodology for setting up, syncing, monitoring, and maintaining honest project data.
No visual demo for this skill
Tooling or audit guidance without a UI surface to embed.
Skill markdown
# Linear Methodology > Keep Linear useful by making it reflect the project, the repository, and the work actually happening. ## What it does - Anchors tracking to the project's North Star and real roadmap. - Sets up or repairs projects, milestones, issues, labels, and dependencies. - Reconciles Linear with repository evidence instead of trusting stale tickets. - Keeps active work current and closes the loop when work ships. ## How it works 1. Read [RESPONSE.md](./RESPONSE.md) for concise, action-first chat. 2. Read [AUTH.md](./AUTH.md), then verify Linear access before any call. 3. Route the request: - Set up, backfill, or start tracking → `linear-setup` - Sync, audit, or rescue a board → `linear-sync` - Check project health → `linear-monitor` - Finish installation → `linear-finish-install` 4. Apply `linear-discipline` throughout the session. 5. Use [METHODOLOGY.md](./METHODOLOGY.md) when the routed skill needs deeper guidance. Default ambiguous requests like “set up Linear tracking” to `linear-setup`.
More from tjcages
- Linear DisciplineKeep Linear tracking honest during development with search-before-create, lifecycle updates, and close-the-loop discipline.
- Linear Finish InstallComplete Linear tracking installation by writing always-on rules and verifying Linear MCP authentication.
- Linear MonitorHealth-check Linear projects for slipping dates, stale in-progress work, orphan issues, and tracking anti-patterns.
- Linear SetupBootstrap or extend Linear project tracking with evidence-based backfill, milestones, dependencies, and repository discipline.
- Linear SyncAudit and rescue an existing Linear project by reconciling its issues, milestones, dependencies, and tracking protocol with repository reality.