hebertzhu Linear
Intent
- Use for Linear issue triage, project updates, sprint planning, workload review, and documentation-linked follow-up work.
Default operating pattern
- Confirm the workspace scope first: team, project, cycle, assignee, labels, or issue identifiers.
- Use the current host's Linear connector or MCP integration to read context before making changes.
- Group related reads together, then batch related writes together so the user can understand the change set.
- For create or update flows, make the target state explicit: status, priority, owner, due date, labels, and linked issues or projects.
- End with a concise handoff: what changed, what still needs confirmation, and the next likely Linear action.
Pack fit
- Included in:
knowledge-ops - Keep requests reusable across product, engineering, and operations workflows.
Boundary
- Do not update issues, projects, or labels before the target team or project is clear.
- Do not pretend a write succeeded without tool output confirming the mutation.