setup-matt-pocock-skills

Standardize repository triage by configuring a consistent state machine for issues using canonical labels like needs-triage and ready-for-agent. This ensures automated engineering agents can reliably track issue states and read architectural context across multiple repositories.

Set up issue tracking and architectural decision records (ADRs) by initializing a standardized domain documentation layout. This establishes a consistent context file structure so AI agents understand the project domain and architectural history from the start.

Yes, this setup requires access to repository root files and CLI tools like gh or glab. These command-line tools are necessary to establish the tracking infrastructure and manage the issue tracker configuration during project initialization and maintenance phases.

Yes, you can use this scaffolding to align context files across different repositories. It eliminates configuration drift by setting up a standardized layout for context files and ADRs, ensuring all engineering skills read your issue tracker and architectural history consistently.

You need a unified triage state machine to prevent configuration drift and ensure consistent metadata management. By using canonical labels, automated tooling and engineering agents can reliably parse issue states and execute subsequent maintenance workflows.

The setup focuses on project initialization and maintenance phases, requiring access to repository root files. If existing repositories have established, non-standard triage vocabularies or documentation structures, applying this standardized layout may require migrating current configurations.