Skills on Brian Faust

Manage Engineering Follow-ups

Sat, 25 Jul 2026 00:00:00 +0000

A checkbox in a pull request is easy to forget once the pull request closes. This skill applies the Engineering Follow-ups Specification so deferred work from a pull request, release, decision, or incident keeps its trigger, owner, deadline, verification procedure, and completion evidence.

Install for Codex

Download the complete skill package or copy and run:

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
curl -fsSL https://wimdy.works/skills/manage-engineering-follow-ups/bundle.tar.gz \
 | tar -xz -C "${CODEX_HOME:-$HOME/.codex}/skills"

Install for Claude Code

mkdir -p "$HOME/.claude/skills"
curl -fsSL https://wimdy.works/skills/manage-engineering-follow-ups/bundle.tar.gz \
 | tar -xz -C "$HOME/.claude/skills"

Invoke directly

$manage-engineering-follow-ups create the two-week production verification from this pull request
/manage-engineering-follow-ups create the two-week production verification from this pull request

Or let ACK construct and validate a draft from pinned evidence:

Write an Incident Postmortem

Sat, 25 Jul 2026 00:00:00 +0000

An incident can be resolved before anyone has proved why it happened. This skill applies the Incident Postmortems Specification to keep facts, reported claims, inferences, hypotheses, and decisions separate. It preserves real uncertainty, requires recovery proof, and moves corrective work into durable Engineering Follow-ups instead of a hopeful checklist.

Install for Codex

Download the complete skill package or copy and run:

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
curl -fsSL https://wimdy.works/skills/write-incident-postmortem/bundle.tar.gz \
 | tar -xz -C "${CODEX_HOME:-$HOME/.codex}/skills"

Install for Claude Code

mkdir -p "$HOME/.claude/skills"
curl -fsSL https://wimdy.works/skills/write-incident-postmortem/bundle.tar.gz \
 | tar -xz -C "$HOME/.claude/skills"

Invoke directly

$write-incident-postmortem draft a reviewed postmortem from these exact incident records
/write-incident-postmortem draft a reviewed postmortem from these exact incident records

Or let ACK construct and validate a draft from pinned evidence:

Prepare an Intent Pull Request

Tue, 21 Jul 2026 00:00:00 +0000

A pull-request description should explain the branch that actually exists, not the branch someone remembers building. This skill applies the Intent Pull Requests Specification to turn the complete diff, Project Profile, and verified decision sources into a review-ready title, body, and portable record. It stops before opening a remote pull request or inventing a claim the evidence cannot support.

Install for Codex

Download the complete skill package or copy and run:

Commit with Intent

Mon, 20 Jul 2026 00:00:00 +0000

A commit should explain what changed without pretending that one word such as fix settles the release decision. This skill combines repository-safe Git packaging with the Intent Commits Specification so type, scope, impact, migration, affected release units, and changeset links stay tied to evidence. After committing, it asks ACK to find missing or contradictory Intent Changesets decisions.

When the existing commit-changes workflow is installed, this skill composes it. It does not replace explicit staging, secret checks, line-length validation, or commit verification, and the package remains usable on its own.

Configure an Intent Project

Mon, 20 Jul 2026 00:00:00 +0000

Without one shared profile, every release tool eventually invents its own names for the same repositories, release units, streams, owners, and gates. This skill creates or reviews the Project Profile used by Intent Commits, Intent Pull Requests, Intent Changesets, Intent Changelog, Release Manifests, Engineering Follow-ups, Incident Postmortems, and ACK. It discovers that policy once instead of duplicating it in each tool.

Install for Codex

Download the complete skill package or copy and run:

Maintain a Release Manifest

Mon, 20 Jul 2026 00:00:00 +0000

A tag tells you what Git points at. It does not prove which artifact was published. This skill applies the Release Manifest Specification to bind a release to its source, changelog, decisions, and artifact digests while saying plainly which remote artifacts were never fetched or verified.

Install for Codex

Download the complete skill package or copy and run:

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
curl -fsSL https://wimdy.works/skills/maintain-release-manifest/bundle.tar.gz \
 | tar -xz -C "${CODEX_HOME:-$HOME/.codex}/skills"

Install for Claude Code

mkdir -p "$HOME/.claude/skills"
curl -fsSL https://wimdy.works/skills/maintain-release-manifest/bundle.tar.gz \
 | tar -xz -C "$HOME/.claude/skills"

Invoke directly

$maintain-release-manifest verify the worker 1.18.3 release
/maintain-release-manifest verify the worker 1.18.3 release

Or let ACK construct and validate a draft from pinned evidence:

Maintain an Intent Changelog

Mon, 20 Jul 2026 00:00:00 +0000

Unreleased should mean ready to publish except for the date, not a pile of fragments someone has to clean up on release day. This skill applies the Intent Changelog Specification , consumes changeset targets, validates and renders them with ACK, and carries verified commit provenance into the correct release-unit records. It keeps canonical release data in the ledger instead of treating generated Markdown as the source of truth.

Install for Codex

Download the complete skill package or copy and run:

Maintain an Intent Changeset

Mon, 20 Jul 2026 00:00:00 +0000

One release decision can span several commits, pull requests, and independently released packages. It still needs one coherent record. This skill applies the Intent Changesets Specification to decide when that record is required, link its commits, and consume every target into the right changelog release. ACK validates the shared profile, identifiers, commit links, targets, and publication gate instead of leaving those checks to memory.

Install for Codex

Download the complete skill package or copy and run: