SuperAPI AI Directory

linear-handbook

General & other

View repository

Updated 10-16 07:19

About this skill

Linear handbook

Turn requirements into Linear work that can be delivered, accepted, and handed off. Select a workflow for the current task and read only the references and templates you need.

Execution

  1. Identify the user's intended outcome and authorized actions.
  2. When current context is needed, read the target issue's current body, relevant recent decisions, and required prerequisite outputs.
  3. Load the appropriate workflow from the task routing below.
  4. Before writing, verify the target ID, actual tool contract, and existing authorization.
  5. After updating, read back the necessary fields and relationships and assess the result against the effective completion criteria.
  • Keep the current goal, adopted conclusions, and links to outputs in the issue body.
  • Record only new information in comments.
  • Keep work at its actual unfinished stage while required acceptance criteria remain unmet.
  • Workflow recommendations do not authorize additional actions or replace confirmed requirements.
  • When an operation's outcome is unknown, follow the recovery workflow before retrying a non-idempotent create operation.

Task routing

The links below are relative to this SKILL.md. Do not resolve them against the current working directory. Product file paths in examples are output locations to replace.

Choose a type template based on the primary deliverable:

  • Restore promised behavior: Bug.
  • Deliver a new capability: Feature.
  • Gather evidence for a decision: Research.
  • Change structure while preserving external behavior: Refactoring.
  • Switch data or usage workflows: Migration.

Environment and evidence

Read policy when actual Workspace, Team, status, responsibility, or automation mappings are needed. Follow applicable existing policy. A missing policy document does not block ordinary drafts or authorized independent work. This edition defaults to English and retains Linear terminology; an explicit user policy may override this default.

Retain each reference's official verification date and applicability limits for feature conclusions. Check current sources and the environment before using dynamic features, plans, or tool fields. Historical documentation does not guarantee that the current connection is available. Examples are synthetic walkthroughs; their acceptance checkboxes express the outcomes to assess in each example.