New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Factory Tickets

by tikalk in tikalk/adlc-team-skills

A skill your agent uses when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.

MITAuto-check passedDevelopment

Install Factory Tickets

skills CLI
$ npx skills add tikalk/adlc-team-skills --skill factory-tickets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tikalk/adlc-team-skills factory-tickets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/factory/factory-tickets .claude/skills/factory-tickets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
factory-tickets
GitHub stars
141
Token cost
~1.2k tokens
SKILL.md length
642 words
Files
1
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.

  • Works in 4 steps: Provider & Identity Discovery → Dual-Authority Paged Queries → Match Evidence (Tracker-Agnostic) → …
  • The user asks for their active worklist — open PRs with next actionable move
  • SKILL.md covers What this skill does, When to use, Operating Process and Invariants & Safety Constraints
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Factory Tickets is an agent skill from tikalk/adlc-team-skills. Use when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.

When your agent uses it

  • The user asks for their active worklist — open PRs with next actionable move
  • Merged work not yet closed
  • Takable tickets
  • Classified by next move

Example prompts

  • “/factory-tickets”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Provider & Identity Discovery
  2. Dual-Authority Paged Queries
  3. Match Evidence (Tracker-Agnostic)
  4. Classify Next Action (Next-Move Sections)

What it can do on your machine

Read from SKILL.md and the folder at commit 2dbed36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Factory Tickets loads about 1.2k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 642 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tikalk/adlc-team-skills at commit 2dbed36, republished under its MIT licence (© tikalk). 642 words, ~1,194 tokens.

Download SKILL.mdSave it as .claude/skills/factory-tickets/SKILL.md (or your agent's skills folder).
name
factory-tickets
description
Use when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.

factory-tickets

What this skill does

factory-tickets is the read-only personal worklist engine of the software factory. It provides the user with an immediate, live, and actionable overview of their active queue, categorized by "next move" rather than abstract status.

It operates directly against the external issue tracker and PR host (GitHub, GitLab, Linear, Jira) using the tracker-agnostic integration layer (factory-mission/references/tracker-integration.md).

When to use

  • At the start of a session or when planning your day, to find out exactly what needs your attention next.
  • To identify which of your pull requests are ready to merge, blocked, or awaiting your review feedback.
  • To discover unassigned, unblocked tickets (spec-gated) that are ready for execution.

When NOT to use:

  • To change ticket status, assignees, or edit bodies (this skill is strictly read-only).
  • To execute or implement tasks (use factory-mission instead).

Operating Process

1. Provider & Identity Discovery
  1. Discover the active tracker provider and credentials (factory-mission/references/tracker-integration.md).
  2. Identify the authenticated user's login. Restrict the search to:
    • Pull requests authored by the authenticated account.
    • Tickets assigned to the authenticated account (or another login if explicitly requested).
2. Dual-Authority Paged Queries

Never poll individual items. Run two paged searches (via MCP or CLI) to fetch the entire active set in one round-trip per source:

  1. Pull Request Search: fetch the user's open PRs, including: draft status, review decision, unresolved threads, named check statuses, and mergeability.
  2. Issue Search: fetch the user's assigned open issues, including: title, description, state, labels, milestones, and linked project metadata.
3. Match Evidence (Tracker-Agnostic)

A PR routinely cross-references multiple tickets. Associate a pull request to a ticket only when there is explicit evidence:

  • A closing link established by the tracker itself.
  • A branch name that contains the ticket number in the repository's convention.
  • A PR title that explicitly names the ticket number. If no explicit evidence exists, leave the association cell empty. Never guess based on mere textual mention.
Show full SKILL.md (326 more words)Show less
4. Classify Next Action (Next-Move Sections)

Assign every retrieved item to exactly one of the following priority sections. Render what was assigned — never reclassify during formatting:

  1. Active Pull Requests (My Turn): Pull requests where the next action belongs to the user:
    • Merge — required checks are green, human approval is complete. Ready-to-merge sorts first (highest priority).
    • Address Review Feedback — changes requested by a reviewer.
    • Fix failing check: <name> — a required CI check has failed (reported by name, not rolled up).
    • Answer N comment threads — unresolved reviewer questions.
    • Finish Draft — PR is still in draft state.
  2. Active Pull Requests (Their Turn): Pull requests waiting on external actions:
    • Awaiting Review — Ready for review, requested reviewer hasn't responded.
    • Awaiting CI — required checks are still running.
  3. Merged, Ticket Still Open: The PR that closes this ticket has merged, but the ticket remains open on the board. Move is: verify, then close.
  4. Takable Now (Backlog): Open issues with lifecycle spec-gated, automation-gating agent-can-execute, and no pull request claiming them. (If empty, display an explicit "none").
  5. Waiting on Someone Else: Open issues with unresolved blocked-by dependencies, naming the blocking ticket.

Note: Epics and parent issues go in an Appendix below a rule, showing child counts and progress. They are never mixed into the active task list.

Invariants & Safety Constraints

  1. Strictly Read-Only: This skill physically cannot edit, comment, create, or modify any ticket, label, assignee, or board field. No gh or glab write commands are present.
  2. No Caching: Every run performs a live fetch. A cached or stale queue is worse than none.
  3. No Rollup Guessing: Never report check status from a rolled-up "failing" commit status if a job was merely cancelled or skipped. Read and name the exact failing context.
  4. Unparsed Word Reporting: If the user's request contains words the query parser doesn't recognize, do not drop them. List them in an "Unparsed Terms" section below the table so the user knows what was ignored.

© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/factory/factory-tickets of tikalk/adlc-team-skills.

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Factory Tickets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Factory Tickets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Factory Tickets this skilltikalk/adlc-team-skills141—~1.2kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo

  • Workspace

    tikalk/adlc-team-skills

    A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…

    141 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed

  • Team Boot

    tikalk/adlc-team-skills

    A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…

    141 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

  • Architect Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

    141 GitHub stars~4.7k tokensUpdated 2 days ago
    Auto-check passed

  • Change Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…

    141 GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed

  • Change Init

    tikalk/adlc-team-skills

    A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.

    141 GitHub stars~3.5k tokensUpdated 2 days ago
    Auto-check passed

  • Change Publish

    tikalk/adlc-team-skills

    A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.

    141 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Factory Tickets

What does Factory Tickets do?

A skill your agent uses when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move. Factory Tickets is an agent skill from tikalk/adlc-team-skills. Use when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.

When should I use Factory Tickets?

Factory Tickets fits situations like: the user asks for their active worklist — open PRs with next actionable move; merged work not yet closed; takable tickets; classified by next move.

How do I install Factory Tickets in Claude Code?

Run `npx skills add tikalk/adlc-team-skills --skill factory-tickets -a claude-code`. Or copy the skill folder (skills/factory/factory-tickets in tikalk/adlc-team-skills) into .claude/skills/factory-tickets in your project. Claude Code loads it when a task matches its description.

How do I install Factory Tickets in Codex?

Run `npx skills add tikalk/adlc-team-skills --skill factory-tickets -a codex`. Or copy the skill folder (skills/factory/factory-tickets in tikalk/adlc-team-skills) into .agents/skills/factory-tickets in your project. Codex loads it when a task matches its description.

Can I use Factory Tickets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill factory-tickets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/factory-tickets, .gemini/skills/factory-tickets, .github/skills/factory-tickets and .opencode/skills/factory-tickets in your project.

What does Factory Tickets need to run?

SKILL.md names no scripts, command-line tools or credentials: Factory Tickets is instructions for the agent only.

Does Factory Tickets access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Factory Tickets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Factory Tickets use?

Factory Tickets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Factory Tickets use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Factory Tickets?

Skills that share tags, products or a category with Factory Tickets: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Factory Tickets?

tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.