imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/skills/setup-engineering-workflows/SKILL.md

setup-engineering-workflows

Skill8 starsChanged 2 months agoMITView on GitHub

Configure repository issue-tracking, triage-label, domain-doc, and agent-instruction conventions. Use when initializing engineering workflows in a repo, configuring GitHub/GitLab issue labels, or establishing CONTEXT.md conventions — even if the user says \"setup our workflows\". Do NOT use for general project package installs.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Single vs Multi-Context Prudence: Default to single-context (CONTEXT.md at root).
line 15
Distinctive:
Preserve Agent Instruction File: If CLAUDE.md or AGENTS.md exists, edit it in-place.
line 16
Very specific:
Conditional Triage Configuration: Only configure triage label files (docs/agents/triage-labels.md) if the triage skill is present in the …
line 17
Very specific:
Action: Check git remote -v, root instruction files (AGENTS.md, CLAUDE.md), docs/adr/, and workspace configurations (pnpm-workspace.yaml, …
line 39
Very specific:
Action: Add or update the ## Agent skills block inside AGENTS.md (or CLAUDE.md):
line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Setup Engineering Workflows

Configure and standardize repository issue-tracking, triage-label vocabularies, domain-modeling architecture (docs/agents/domain.md), and agent instructions (AGENTS.md / CLAUDE.md).

Core Invariants

Prompt-Driven Exploration: Inspect existing remotes, directories, and labels before proposing changes; do not blindly overwrite existing tracker setups.
Single vs Multi-Context Prudence: Default to single-context (CONTEXT.md at root); only suggest multi-context (CONTEXT-MAP.md) when monorepo signals (workspaces, packages/*) are detected.
Preserve Agent Instruction File: If CLAUDE.md or AGENTS.md exists, edit it in-place; if neither exists, ask the user before creating one. Never create both.
Conditional Triage Configuration: Only configure triage label files (docs/agents/triage-labels.md) if the triage skill is present in the repository.
Durable Workspace Documentation: Persist all configured decisions into docs/agents/issue-tracker.md, docs/agents/domain.md, and docs/agents/triage-labels.md.

Architecture & Map of Content (MOC)

[ Codebase Inspection (Remotes, Monorepos) ] ──► [ Interactive Setup Sections A/B/C ] ──► [ Update AGENTS.md / docs/agents/ ]

Component	Responsibility	Seed Template
Issue Tracker Config	GitHub (`gh`), GitLab (`glab`), or Local Markdown	`skills/setup-engineering-workflows/issue-tracker-github.md`
Triage Vocabulary	5 canonical roles mapping to repo labels	`skills/setup-engineering-workflows/triage-labels.md`
Domain Docs Layout	Single-context vs multi-context conventions	`skills/setup-engineering-workflows/domain.md`

Step-by-Step Procedure (TWI)

Step 1: Autonomous Repository Exploration

Action: Check git remote -v, root instruction files (AGENTS.md, CLAUDE.md), docs/adr/, and workspace configurations (pnpm-workspace.yaml, packages/).
Key Point: Identify whether the repository already has a tracker or triage convention.
Why: Avoids re-asking the user for facts already evident in git and configuration files.

Step 2: Configure Issue Tracker & Triage Labels

Action: Present recommendations section-by-section:
- Section A (Tracker): GitHub (gh), GitLab (glab), or Local Markdown (.scratch/).
- Section B (Labels): Canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).
- Section C (Domain): Single-context vs. Multi-context.
Inline Checklist:
- Tracker confirmed and documented in docs/agents/issue-tracker.md
- Triage labels mapped in docs/agents/triage-labels.md
- Domain doc rules written to docs/agents/domain.md

Step 3: Wire Instructions into AGENTS.md / CLAUDE.md

Action: Add or update the ## Agent skills block inside AGENTS.md (or CLAUDE.md):

## Agent skills

### Issue tracker
[Summary of issue tracking]. See `docs/agents/issue-tracker.md`.

### Domain docs
[Single or multi-context]. See `docs/agents/domain.md`.

Why: Context pointers ensure newly spawned subagents read repository conventions immediately.

Anti-Rationalization Guardrails

Tempting Rationalization	Binding Rule	Engineering Rationale
"Create both AGENTS.md and CLAUDE.md for maximum coverage."	Forbidden. Maintain exactly one canonical agent file.	Multiple instruction files lead to configuration drift and conflicting rules.
"Force multi-context on single-package repositories."	Default to single-context unless monorepo exists.	Unnecessary multi-context structures create excessive directory nesting.
"Overwrite existing custom issue labels without asking."	Map existing repo labels to canonical roles.	Overwriting existing team labels breaks active project boards and workflows.

Download now (ZIP)

In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-data-remediationSkill
- ai-engineeringSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- engineering-workflow-guideSkill
- git-safety-guardrailsSkill
- goalSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- j-spaceSkill
- migrate-to-shoehornSkill
- ml-best-practicesSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- retroSkill
- scaffold-exercisesSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- skill-conductorSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- workflow-designerSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free