tachyon-linearlisted

# Tachyon Linear Use this skill when operating Linear through the local `tachyon` CLI. ## Rules - Use the real `tachyon` CLI. Do not use direct Linear API calls or GitHub issues. - Prefer `tachyon linear issue ...` for Linear-specific work. - Use `tachyon issue ... --provider linear` only when the user explicitly wants the default project-management abstraction. - For mutations, confirm the exact title, description, team, status, priority, assignee, and due date unless the user already provided them clearly. - Always pass an explicit `--tenant-id` when the tenant/operator is known from the task, URL, repo, or user context. - For Tachyon Apps project work, use team `プラットフォーム事業` when the user has not specified another Linear team. - Use `--json` when creating, listing, or updating so the result can be parsed and summarized accurately. - Treat API tokens, auth headers, and credential refresh output as secrets. Do not echo them back. ## Orientation Check CLI availability and auth before doing live work: ```bash command -v tachyon tachyon auth list tachyon linear --help tachyon linear issue --help ``` Inspect subcommand options before using unfamiliar fields: ```bash tachyon linear issue create --help tachyon linear issue list --help tachyon linear issue update --help ``` ## List Issues List active Linear issues for a team: ```bash tachyon linear issue list \ --team "プラットフォーム事業" \ --tenant-id <tenant_id_or_alias> \ --json ``` Include completed or canceled issues