setup-matt-pocock-skills

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.

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.

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.

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.

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.

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.