setup-matt-pocock-skills

Name: setup-matt-pocock-skills
Availability: InStock
Author: Spontus

Configure repository conventions for issue trackers, triage labels, and domain documentation.

1|Updated May 22, 2026

Search Tags:#issue tracker #configuration #repo setup #engineering workflows #triage labels #domain docs #ADR navigation

Ready to run

npx skills add https://github.com/spontus-reach/spontus --skill setup-matt-pocock-skills-spontus-reach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/spontus-reach/spontus/tree/main/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/spontus-reach/spontus --skill setup-matt-pocock-skills-spontus-reach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents engineering skills from operating with missing or incorrect repo-specific context by establishing the expected configuration in the repository (issue tracker details, triage label vocabulary, and domain doc layout).

Core Features & Use Cases

Issue tracker configuration: Documents whether issues/PRDs are handled via GitHub, GitLab, local markdown, or another workflow, so downstream skills know how to create, fetch, and comment correctly.
Triage label vocabulary mapping: Captures the five canonical triage roles and maps them to the exact label strings used in this repo’s tracker to avoid label mismatches or duplicates.
Domain documentation consumption rules: Clarifies whether the repo is single-context or multi-context and how skills should read CONTEXT.md, CONTEXT-MAP.md, and ADRs to use consistent project vocabulary and surface ADR conflicts.

Quick Start

Run the setup-matt-pocock-skills skill and answer the three configuration questions (issue tracker, triage labels, and domain doc layout) one at a time.

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 repo context for engineering workflows and issue triage?▼

Configuring repo context involves documenting issue tracker details, mapping triage label vocabulary, and defining domain doc layout so downstream engineering skills can reliably operate without missing project context. This setup ensures skills know how to fetch issues and navigate ADRs correctly.

What is the best way to map triage labels to my repository's issue tracker?▼

Mapping triage labels requires capturing five canonical triage roles and assigning them to the exact label strings used in your specific tracker. This prevents label mismatches or duplicates when downstream skills attempt to automatically triage issues or PRDs.

How do downstream skills read CONTEXT.md and ADR navigation files correctly?▼

Downstream skills read CONTEXT.md and ADRs by following domain documentation consumption rules established during setup. These rules clarify whether the repo is single-context or multi-context and specify how to use consistent project vocabulary while surfacing ADR conflicts.

Does this configuration work with both GitHub and GitLab issue trackers?▼

Yes, the configuration supports GitHub, GitLab, local markdown, or another workflow. Documenting your specific issue tracker during setup ensures downstream skills know how to correctly create, fetch, and comment on issues or PRDs without integration errors.

Why do engineering skills lack correct context about my issue tracker and labels?▼

Engineering skills lack correct context when repository-specific conventions for the issue tracker, triage labels, or CONTEXT and ADR layout have not been established. Applying configuration updates the repo agent file with an Agent skills block to resolve this.

When should I run a repo setup configuration for engineering workflows?▼

You should run repo setup configuration during initial adoption of engineering skills or when existing skills appear to lack correct context about the issue tracker, label vocabulary, or domain documentation layout. This ensures downstream workflows have accurate operational instructions.