Skills For Real Engineers

Editor Review

A framework that owns the whole development process is hard to fix when one step goes wrong. These skills are intentionally small, so you can edit one and stack them. Grilling skills keep asking until the branches of a design are resolved. The docs variant also maintains a glossary and decision records so later code uses the same words. Implementation then uses a failing-test-first skill and a phased bug diagnosis. A spec can be published to the issue tracker or kept in a local file. It fits engineers who want to keep the process and only hand the steps that keep failing to a skill.

AI Tools Navigator Editorial TeamUpdated: 2026-10-09

What is Skills For Real Engineers

Skills For Real Engineers is a set of editable agent skills published by Matt Pocock. They align a change before coding, build a project glossary, and constrain implementation with tests and diagnosis. Some skills run only when a person invokes them and orchestrate the work. Others hold a reusable discipline the assistant may also invoke when the task fits. Engineering skills include grilling, writing a spec, splitting tickets, and implementation. Productivity skills include handoff documents and restating a message that did not land. Each repository needs a one-time setup skill.

Skills For Real Engineers Key Features

Grill until the design lines up

grill-me keeps asking until every branch of a plan is resolved. grill-with-docs also updates the glossary and architecture decision records.

Specs and tracer tickets

to-spec turns the conversation so far into a spec. to-tickets splits that into small tickets that declare what blocks them.

Test-first work and bug diagnosis

tdd builds one vertical slice at a time with a failing test first. diagnosing-bugs starts by building a feedback loop that reproduces the bug.

One setup pass per repository

The setup skill asks which issue tracker, triage labels, and doc locations to use. The other engineering skills depend on those answers.

Skills For Real Engineers Key Advantages

The skill files are editable, so a project can change them to match local habits

Grilling and writing a spec are separate, so implementation does not start while the discussion is still open

Code review checks both repository standards and whether the diff matches the original spec

Setup asks whether the issue tracker is a hosted service or local files before tickets are written

Skills For Real Engineers Use Cases

Align terms before a change

Before changing a module, an engineer runs the docs grilling skill, files vague words into the glossary, and only then settles the spec.

Implement tickets and review

After the spec is settled, the implement skill writes tests at the agreed seams, then a code review checks the diff against the spec before commit.

Hand a session to the next assistant

When the conversation is too long, the handoff skill compacts it into a document so another assistant can continue.

Frequently Asked Questions

▶How do these skills differ from a framework that owns the whole process?

The repository says some methods take over the whole process, which makes a bug in the process hard to fix. These skills are meant to stay small and composable, editable per repository, and not tied to one model. User-invoked skills orchestrate. Model-invoked skills hold a discipline the assistant may also reach for. A user-invoked skill may call a model-invoked one, but not another user-invoked skill.

▶Why is there a setup step after install?

The engineering skills depend on choices stored for the repository. The setup skill asks three things: whether the issue tracker is a hosted service, local files, or something else you describe; which labels triage uses; and where documents should be saved. Run it once per repository. The docs grilling skill writes terms into the glossary and hard decisions into decision records. Without setup, those skills do not know where tickets and documents go.

▶Which skill does the repository suggest when the code is still wrong?

The readme splits the failures. Use grilling when the requirement is not aligned. Use the glossary when the agent is too wordy, so code and conversation share one vocabulary. When code runs wrong, the failing-test-first skill builds a feedback loop, and the diagnosis skill reproduces the bug, narrows it, states a hypothesis, adds instrumentation, fixes it, and adds a regression test. When the design turns to mud, the architecture skill lists modules that could be deepened.

Skills For Real Engineers

Editor Review

What is Skills For Real Engineers

Basic Info

Best For