agentleFS
Davidengstrom01Davidengstrom01/claude-skills/skills/ticketed/SKILL.md

ticketed

Skill0 starsChanged 41 days agoMITView on GitHub

Create Jira tickets assigned to David in the current sprint with a Background + Acceptance criteria description. Use on 'ticketed', 'create a ticket', 'make a Jira issue'.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create Jira tickets through the Atlassian Rovo tools.

    line 8
  2. Distinctive:

    If the user's input contains solution details, leave them out of the ticket and mention in one line that they were left out.

    line 28
  3. Distinctive:

    Use project key NOVA unless the user named another project.

    line 51
  4. Very specific:

    Read the sprint id from the result.

    line 54
  5. Distinctive:

    If no active sprint is found, tell the user and ask whether to create the ticket without a sprint.

    line 55
  6. Distinctive:

    Check the draft against the core principle and remove anything that describes how.

    line 57
  7. Very specific:

    Create the ticket with createJiraIssue: set assignee to the account id and the sprint field to the sprint id (a number).

    line 59
  8. Distinctive:

    If the user describes several tickets, draft them all, confirm once, then create each.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ticketed

Create Jira tickets through the Atlassian Rovo tools. Every ticket is assigned to the current user and placed in the active sprint.

Rules

  • Project: NOVA by default. Use another project only if the user names one.
  • Assignee: always the current user (atlassianUserInfo → account id).
  • Sprint: always the active sprint of the target project's board.
  • Description: always the exact format below. No other sections.
  • Issue type: Task unless the user says Bug, Story or similar.
  • Language: write the ticket in the language the user uses.

Core principle: what, never how

A ticket describes the current state and the desired state. It never explains how to solve it; that is for the developer to work out.

Never include:

  • implementation steps, technical approaches or suggested solutions
  • code, class, method, file or library names as instructions
  • phrases like "add a", "refactor", "use X to", "implement by"

If the user's input contains solution details, leave them out of the ticket and mention in one line that they were left out.

Description format

## Background
<Current state: how things are today, plus a short reason why it needs to change. 1-4 sentences.>

## Acceptance criteria
- [ ] <Desired state: an observable, testable outcome>
- [ ] <...>
  • Background: current state + short reason for the change. No solution.
  • Acceptance criteria: the desired state as verifiable outcomes. Describe what is true when done, never how to get there.

Example:

  • Good: "- [ ] A user who is removed from a team no longer receives that team's notifications."
  • Bad: "- [ ] Add a check in NotificationHandler that filters removed members."

Steps

  1. Get cloudId with getAccessibleAtlassianResources and the user's account id with atlassianUserInfo.
  2. Use project key NOVA unless the user named another project.
  3. Find the active sprint:
    • searchJiraIssuesUsingJql with project = <KEY> AND sprint in openSprints(), maxResults 1, requesting the sprint field (usually customfield_10020).
    • Read the sprint id from the result. If there are several open sprints, pick the one with state active.
    • If no active sprint is found, tell the user and ask whether to create the ticket without a sprint.
  4. Draft the summary and description from what the user provided. If the current state, reason or desired state is missing, ask for it. Do not invent it.
  5. Check the draft against the core principle and remove anything that describes how.
  6. Show the draft (type, project, summary, description) and ask for confirmation.
  7. Create the ticket with createJiraIssue: set assignee to the account id and the sprint field to the sprint id (a number). If the sprint cannot be set at creation, set it with editJiraIssue right after.
  8. Reply with the ticket key and link in one line.

Multiple tickets

If the user describes several tickets, draft them all, confirm once, then create each.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.