setup-matt-pocock-skills

Configure repo-specific issue tracker, triage labels, and domain-doc layout in AGENTS.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill setup-matt-pocock-skills-kileroppo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill setup-matt-pocock-skills-kileroppo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents engineering and planning skills from operating with missing or incorrect repo-specific context by setting up the shared “Agent skills” configuration that those skills expect.

Core Features & Use Cases

  • Issue tracker setup: Records where issues and PRDs live (GitHub, GitLab, or local markdown) so downstream skills can create, fetch, and update tickets correctly.
  • Triage label vocabulary mapping: Defines the canonical triage role label strings so triage state transitions don’t create duplicate or mismatched labels.
  • Domain docs layout guidance: Establishes how domain concepts are discovered and how ADRs/CONTEXT are consumed (single-context vs multi-context), improving consistency in planning and implementation.

Quick Start

Run the setup skill before using to-issues, to-prd, triage, diagnose, tdd, improve-codebase-architecture, or zoom-out so the repo’s issue tracker, label vocabulary, and domain-doc conventions are correctly recorded.

Frequently Asked Questions about setup-matt-pocock-skills

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

FAQPage Schema
How do I configure issue tracker settings and triage labels for an AI agent in my repository?

Domain docs layout guidance establishes how domain concepts are discovered and how ADRs and CONTEXT files are consumed, recording these conventions in reference files under docs/agents/ so planning and implementation skills maintain consistent architectural context.

How do I set up domain documentation and ADR conventions for engineering planning agents?

Domain docs layout guidance establishes how domain concepts are discovered and how ADRs and CONTEXT files are consumed, recording these conventions in reference files under docs/agents/ so planning and implementation skills maintain consistent architectural context.

Why do my engineering agents use incorrect issue tracker or label assumptions when working on my repo?

Engineering agents use incorrect tracker or label assumptions when the repo-specific "Agent skills" configuration is missing, which this Skill resolves by interactively exploring existing files and writing tracker locations and triage label vocabulary into AGENTS.md or CLAUDE.md.

Can I use this setup skill to configure agent skills for both GitHub and GitLab issue trackers?

Yes, you can use this setup skill to configure agent skills for GitHub, GitLab, or local markdown issue trackers, recording where issues and PRDs live so downstream skills can create, fetch, and update tickets correctly across platforms.

Will configuring repository agent skills break my existing user edits in AGENTS.md or CLAUDE.md?

Configuring repository agent skills will not break existing user edits, as the Skill interactively explores existing repo files and safely appends the "Agent skills" block plus docs/agents/ reference files without overwriting your current configurations.