agent-issue-tracker-setup

Configures a repository's AGENTS.md with a tracker-agnostic issue workflow.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/csackrider/AI-DLC --skill agent-issue-tracker-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-issue-tracker-setup
Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/agents/agent-issue-tracker-setup
Command: npx skills add https://github.com/csackrider/AI-DLC --skill agent-issue-tracker-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboards a consumer repository to adopt AIDLC in a way that is issue-tracker-agnostic for phase skills: the repo declares which system holds Feature work, and you leave a durable record in AGENTS.md.

Core Features & Use Cases

  • Issue-tracker agnosticism: outputs a durable AGENTS.md contract that works across GitHub, Linear, and Jira.
  • Guided wiring: references ISSUE-TRACKER-PORTABILITY docs and AGENTS.md template to align with team processes.
  • Human-driven setup: does not perform API calls; guides humans to wire the tracker.
  • Use Case: A team migrating from GitHub Issues to Linear can follow the template to capture the mapping in AGENTS.md.

Quick Start

Configure the consumer repo by selecting the source-of-truth tracker and populating the AGENTS.md block using the template.

Frequently Asked Questions about agent-issue-tracker-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize issue-tracker setup in AGENTS.md for multiple platforms?

Standardize issue-tracker setup by applying a tracker-agnostic contract in AGENTS.md that works across GitHub, Linear, and Jira. The onboarding process populates a consumer-specific table and references docs to create a durable specification aligned with ISSUE-TRACKER-PORTABILITY.

What is the best way to document issue-tracker migration steps in a repository?

Document issue-tracker migration steps by capturing the source-of-truth tracker mapping in AGENTS.md using a standardized template. This creates a durable record that ensures phase skills remain tracker-agnostic while preserving clear migration steps for team processes.

Can I use this issue-tracker onboarding template with Jira and Linear?

Yes, this issue-tracker onboarding template works with Jira, Linear, and GitHub Issues. It outputs a tracker-agnostic AGENTS.md contract that declares which system holds Feature work, ensuring portability across different tracking platforms.

Does the AGENTS.md issue-tracker setup require API calls to configure?

No, the AGENTS.md issue-tracker setup is a human-driven process that does not perform API calls. It guides users to wire the tracker manually by selecting the source-of-truth tracker and populating the AGENTS.md block using the provided template.

Why does my repository need an issue-tracker contract for AIDLC adoption?

Your repository needs an issue-tracker contract for AIDLC adoption to ensure phase skills can interact with your tracking system consistently. Declaring the source-of-truth tracker in AGENTS.md provides a durable, tracker-agnostic specification that aligns with team processes.