setup-matt-pocock-skills

Configure repository issue tracking, triage labels, and domain documentation layout.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/Soham407/studio-kickstart --skill setup-matt-pocock-skills-soham407
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/Soham407/studio-kickstart/tree/main/architecture/matt-pocock-setup-matt-pocock-skills
Command: npx skills add https://github.com/Soham407/studio-kickstart --skill setup-matt-pocock-skills-soham407

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill prevents engineering agent workflows from failing due to missing or mismatched per-repo context, such as the issue tracker location, triage label vocabulary, and where domain documents live.

Core Features & Use Cases

  • Issue tracker setup: Records whether issues and PRDs live on GitHub, GitLab, or locally as markdown, so downstream skills can publish, fetch, and follow the correct workflow.
  • Triage label mapping: Establishes the five canonical triage role strings and maps them to the label names actually used in the repo.
  • Domain docs consumption rules: Defines whether the repo is single-context or multi-context so skills can locate CONTEXT.md/CONTEXT-MAP.md and ADRs correctly.
  • Designed for prompt-driven confirmation: Gathers evidence from the repo (e.g., existing AGENTS.md/CLAUDE.md sections and current conventions) and then asks the user to confirm the three decisions before writing.

Quick Start

Ask the AI to run setup-matt-pocock-skills to configure your repo’s issue tracker, triage labels, and domain-doc layout based on what already exists in your repository.

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 agent context for issue tracking and triage labels in my repository?

To configure agent context, you need to set up repository-specific files like AGENTS.md or CLAUDE.md. This skill interactively explores your repo layout and writes the agent skills block to map issue trackers, triage labels, and domain docs.

What is domain documentation discovery and how does it work with single-context versus multi-context layouts?

Domain documentation discovery locates CONTEXT.md, CONTEXT-MAP.md, and ADRs. You define whether your repo uses a single-context or multi-context layout so downstream agent skills can correctly find and consume these domain documents.

Do I need to manually edit AGENTS.md or CLAUDE.md to set up GitHub or GitLab issue trackers for agents?

No, you do not need to manually edit these files. The skill gathers evidence from existing conventions and prompts you to confirm tracker modes before automatically writing the required configuration blocks.

What's the best way to initialize agent workflows for diagnosing issues and improving codebase architecture?

The best way is to first establish the per-repo context. This setup skill records your tracker location and triage vocabulary so downstream workflows like diagnose, tdd, and improve-codebase-architecture function correctly.

Why do engineering agent workflows fail when running triage or generating PRDs?

Agent workflows fail due to missing or mismatched per-repo context, such as undefined issue tracker locations or unmapped triage labels. Configuring these repository-specific settings prevents downstream skill execution errors.

Can I use local markdown files instead of GitHub or GitLab for my agent issue tracker?

Yes, you can use local markdown files. The skill records whether issues and PRDs live on GitHub, GitLab, or locally as markdown, ensuring downstream skills follow the correct publishing and fetching workflow.