Stats
Actions
Tags
From spectatr-tools
Use when creating, updating, or organizing work items in Linear — covers when to create Initiatives vs Projects vs Issues, labeling rules, and hierarchy conventions for SpectatrAI. Triggers on any Linear MCP tool call, issue triage, project planning, or work item creation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spectatr-tools:linear-conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
All Linear work follows a strict hierarchy: **Initiative (WHY) → Project (WHAT) → Issue (HOW)**. Every work item must be created at the correct level with proper labels.
All Linear work follows a strict hierarchy: Initiative (WHY) → Project (WHAT) → Issue (HOW). Every work item must be created at the correct level with proper labels.
Initiative (WHY — company goal)
→ Project (WHAT — a deliverable)
→ Issue (HOW — a single task)
| Concept | What it is | Example |
|---|---|---|
| Initiative | Company-level goal/objective. Groups multiple projects. | "Scale B2B Platform for Enterprise Clients" |
| Project | Concrete deliverable with outcome and target date. Contains issues. | "Axis B2B - Face Recognition Module" |
| Issue | Single task — bug, feature, improvement, or tech debt. | "Add batch upload endpoint for face embeddings" |
| Project Label | Tag on projects to filter by product. | Axis B2B, Pulse, Jordy |
| Issue Label (Product) | Tag on issues identifying which product. | Axis B2B, Pulse, Jordy |
| Issue Label (Type) | Tag on issues classifying kind of work. | Bug, Feature, Tech Debt, DevOps |
Decision rules:
| Scenario | Action |
|---|---|
| Company-wide goal spanning multiple projects | Create an Initiative |
| New feature / major deliverable | Create a Project (under an Initiative if one exists) |
| Task within an existing project | Create an Issue inside that Project |
| Standalone bug or small fix (no project context) | Create a standalone Issue with Product + Type labels |
| Maintenance on product with no active project | Create a standalone Issue with Product + Type labels |
| Product deployed, no work happening | Nothing — labels exist for when work comes up |
Every issue MUST have both:
Every project MUST have:
Initiatives do not carry labels — they are organizational containers only.
If a standalone issue grows into multiple tasks, promote it to a Project. Create the Project, move the original issue inside it, and add new issues as needed.
Product labels (Issues & Projects):
Type labels (Issues only):
All issues go to the Product Engineers team unless specified otherwise.
Initiative: "Launch Pulse 2.0" ← company goal
├── Project: "Pulse - Live Clipping" ← deliverable (project label: Pulse)
│ ├── Issue: "Support 9:16 aspect ratio" (labels: Pulse + Feature)
│ ├── Issue: "Add clip metadata export" (labels: Pulse + Feature)
│ └── Issue: "Fix stream disconnect bug" (labels: Pulse + Bug)
│
└── Project: "Pulse - AI Highlights" ← deliverable (project label: Pulse)
├── Issue: "Train highlight model v3" (labels: Pulse + Feature)
└── Issue: "Build highlights review UI" (labels: Pulse + Feature)
Standalone (no project):
└── Issue: "Web-Fantasy - Fix login timeout" (labels: Web-Fantasy + Bug)
npx claudepluginhub spectatr-ai/spectatr-claude-pluginsCreates structured Linear issues (1 main + N sub-issues) with project linking, title prefixing, and labeling. Supports two workflows: Generic (code tasks) and PRD Pipeline (Korean-language product requirements with content strategy principles).
Interact with Linear to view, create, and update issues using MCP or the Linear CLI, with varlock-based secret management.
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.