setup-matt-pocock-skills

Discover repository conventions and draft missing issue tracker and documentation layouts.

779|80|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Haohao-end/openagent --skill setup-matt-pocock-skills-haohao-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/setup-matt-pocock-skills
Command: npx skills add https://github.com/Haohao-end/openagent --skill setup-matt-pocock-skills-haohao-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly establish a clean, editable repository-level engineering context when the repo lacks a defined issue tracker, triage taxonomy, or domain documentation layout.

Core Features & Use Cases

  • Repository context discovery first: Investigates the existing repository structure instead of assuming defaults.
  • Triage and issue workflow setup: Produces configuration drafts for issue tracking and labeling vocabulary when missing.
  • Domain document layout scaffolding: Proposes an organized documentation layout tailored to the repository’s needs.

Use case: When onboarding a new engineering process for an existing codebase—before writing detailed PRDs or implementing features—you can generate consistent triage tags, issue workflow guidance, and documentation structure.

Quick Start

Use the setup-matt-pocock-skills skill to prepare a repository configuration draft by first inspecting the current repo state and then proposing an issue tracker and documentation layout only where gaps are found.

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 bootstrap repository-level engineering workflows for a new codebase?

Setting up repository-level engineering workflows involves discovering existing repo conventions and drafting missing issue tracker configurations, triage tags, and domain documentation layouts to prepare the codebase for structured feature development.

When do I need to scaffold a domain documentation layout for my repository?

You need to scaffold a domain documentation layout when onboarding a new engineering process for an existing codebase that lacks defined structure, ensuring organized documentation before writing detailed PRDs or implementing features.

Can I set up triage tags and issue tracking without assuming GitHub Issues?

Yes, you can set up triage tags and issue tracking without assuming GitHub Issues, because the workflow configuration requires no specific platform assumptions, supports multiple contexts, and separates configuration from implementation details.

What is the best way to establish engineering process setup for early-stage repositories?

The best way to establish early-stage engineering process setup is to investigate the existing repository structure first, proposing an issue tracker and documentation layout only where gaps are found, creating a clean and editable context.

Does repository setup configuration separate workflow rules from implementation details?

Yes, repository setup configuration strictly separates workflow rules from implementation details, ensuring that issue tracking guidance and triage taxonomy remain independent of specific codebase implementation choices.