Skip to main content
Use the HireData Linear Issues skill to turn a bug, customer request, prototype, recording, meeting note, or technical prompt into an issue that is complete for its current maturity. The skill contains HireData’s issue-writing method, templates, refinement guidance, and a maintained snapshot of the relevant workflow rules. It supports both HireData team members and approved partners. Access to live Linear issues and Notion pages still depends on the permissions of the connected account.
Installing the skill does not grant access to HireData’s Linear workspace, Notion pages, customer data, or projects. It uses only the sources you are already authorized to access.

Who can use it

HireData can share selected Notion pages with a partner when closer collaboration is useful. The same skill then follows those shared sources without exposing unrelated internal pages.

Before you begin

Install or update the HireData plugin and start a new conversation so your assistant loads the latest skill. Prepare as much of the following evidence as you have:
  • The affected user, account, workflow, or object
  • The relevant environment and page URL
  • Exact reproduction steps for a bug
  • What happened and what you expected
  • Frequency, impact, and any workaround
  • Screenshots, recordings, timestamps, runs, events, or logs
  • The original request or conversation
You do not need every item before starting. The skill identifies material gaps without inventing answers.

Draft before changing Linear

Start with:
In Claude Code, the installed skill may appear as /hiredata:hiredata-create-linear-issues. The draft includes:
  1. A proposed title
  2. The correct route: intake, product specification, implementation, or delivery
  3. An honest readiness level
  4. A structured description with evidence and source links
  5. Missing information and open decisions
  6. Duplicate, dependency, and related-work recommendations when they can be verified
  7. Proposed metadata only when an approved source supports it

Example prompts

Report a bug

Refine a feature

Prepare work for engineering

Work as an approved partner

Apply an approved update

How the skill treats complex work

For broad or prototype-led features, the skill:
  • keeps the issue understandable without opening the prototype;
  • separates predetermined behaviour from model-judged behaviour;
  • states whether capabilities coexist, are mutually exclusive, or run in order;
  • covers or explicitly defers configuration, execution, storage, presentation, reporting, automation, failure handling, regression, and rollout;
  • separates reusable product behaviour from customer-specific wiring;
  • keeps product specifications and engineering implementation issues distinct when appropriate.

Review and responsibility

AI-assisted does not mean automatically approved. The reporter remains responsible for facts, evidence, and customer context. HireData’s normal Triage, refinement, estimation, and planning process still applies. Before submitting or approving a live change, check that the issue:
  • describes the observable problem or outcome;
  • distinguishes facts, decisions, assumptions, and open questions;
  • links the original evidence;
  • does not invent urgency, ownership, estimates, implementation details, or acceptance criteria;
  • uses only sources and actions available within the user’s existing permissions.

Privacy and security

  • Share only the customer and candidate data needed to understand or reproduce the issue.
  • Never include credentials, access tokens, secrets, or unrelated personal data.
  • Do not paste security vulnerabilities into a public GitHub issue. Contact HireData privately through your normal support channel.
  • A public skill source does not make private Notion pages or Linear issues public. Their existing permissions continue to apply.

Troubleshooting

  • The skill is missing: update the HireData plugin and start a new conversation.
  • The assistant cannot open a Notion page: ask HireData whether that page should be shared with your account, or continue using the bundled snapshot and mark the result unverified.
  • The assistant wants to change Linear immediately: say “Draft only” unless you intend and are authorized to make the live change.
  • A workflow rule looks stale: ask the assistant to check the canonical shared Notion page before applying metadata.
  • The assistant cannot search Linear: it can still produce a complete report; duplicate and relationship checks remain unverified.
The skill source is available at github.com/HireData/skills.