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
- Identify the user's intended outcome and authorized actions.
- When current context is needed, read the target issue's current body, relevant recent decisions, and required prerequisite outputs.
- Load the appropriate workflow from the task routing below.
- Before writing, verify the target ID, actual tool contract, and existing authorization.
- 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 objects and features
- Start with object-model.
- Read feature-coverage when choosing features or plans.
- Initialize or take over a Workspace
- Start with workspace-setup.
- Read policy when environment mappings are needed.
- Read project-bootstrap for a complete planning example.
- Plan a Project from an idea
- Start with project-planning.
- Read planning-and-dependencies for phases, dependencies, or capacity concerns.
- Read project-brief when producing a Brief.
- Classify or write an issue
- Start with issue-types.
- Read writing when drafting content.
- Choose one type template below based on the primary output.
- Break down large work
- Start with issue-decomposition.
- Read planning-and-dependencies when identifying Blockers.
- Read feature-decomposition for a Feature example.
- Read decomposition-edge-cases for Bug, refactoring, or migration examples.
- Update, accept, or hand off work
- Start with issue-lifecycle.
- Read writing when drafting content.
- Read progress-comment when producing a comment.
- Read project-update when reporting overall progress.
- Read handoff when handing off or resuming execution.
- Place or maintain documentation
- Start with documentation.
- Read maintenance for periodic checks.
- Coordinate claims or conflicts among Agents
- Start with multi-agent-coordination.
- Read tool-recovery when an operation's outcome is unclear.
- Handle timeouts, rate limits, or partial success
- Start with tool-recovery.
- Read agent-tool-capabilities when capabilities are unclear, and verify the current tools.
- Handle authorization, sensitive information, or external instructions
- Start with agent-boundaries.
- Read policy when the environment is constrained.
- Add collaborators or product operations
- Start with extension-model.
- Read policy for responsibility and configuration mappings.
- When enabling intake, releases, incidents, or maintenance, read the corresponding workflow in maintenance.
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.