riekelt writes skills that guide an AI agent through engineering work, with a focus on documentation and decision-making around software systems. Their most popular skills cover documenting HTTP APIs, message payloads, DTOs and webhooks, documenting legacy codebases whose docs are stale, enforcing architecture boundaries, reviewing specs and plans before execution, vetting dependencies, and recording decisions as ADRs. What stands out is the consistent emphasis on evidence, explicit contracts and recorded reasoning over assumption.
Multi Agent Review
1 skills · 63 stars
Multi Agent Review Use when a spec or plan needs review before execution begins - "review my spec", "is this plan re…
Technical Writer
11 skills · 34 stars · MIT
Diagramming Processes Use when a business process, workflow, lifecycle, or interaction between systems needs a diagram…
Documenting Contracts Use when documenting an HTTP API, message payloads, queue contracts, DTOs, file formats, or webho…
Documenting Legacy Codebases Use when documenting an existing codebase whose documentation is missing, stale, or untrusted - a…
Recording Decisions Use when a decision needs recording - an ADR, a decision log entry, or when someone asks to write…
Reviewing Technical Prose Use when reviewing, rewriting, or editing someone else's technical text, when writing a review re…
Technical Writing Use when writing, restructuring, or revising any technical document - specs, design docs, READMEs…
Writing Changelogs Use when writing a changelog entry, release notes, or a "what shipped" summary after completing w…
Writing Design Docs Use when writing a proposal, RFC, design document, spec, or migration plan - anything that argues…
Writing Issues Use when writing or refining tracker items - epics, stories, tasks, bug reports, spikes, or accep…
Writing Postmortems Use when writing a postmortem, incident report, or root-cause analysis after an outage, a defect…
Writing Runbooks Use when writing operational documentation - runbooks, setup guides, release procedures, migratio…
Principal Engineer
11 skills · 7 stars
Adding Dependencies Use when about to add, update, vet, or remove a dependency - a package, library, SDK, GitHub acti…
Grounding Before Coding Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - be…
Guarding Architecture Use when a change crosses module boundaries, adds a dependency direction between modules, touches…
Handling Failures Use when writing or touching any error path, catch block, fallback, default value, retry, or degr…
Keeping One Source Of Truth Use when adding data, config, state, constants, an enum-like string, a cache, or anything that co…
Operating Safely Use when an action touches live systems, shared state, or things that do not come back - deleting…
Principal Engineering Use when doing any non-trivial engineering work - implementing, debugging, refactoring, configuri…
Scoping Changes Use when deciding how big a fix should be, when scope is drifting mid-task, when a plan is being…
Testing Changes Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior chan…
Verifying Before Done Use when about to say \"done\", \"fixed\", \"passing\", or \"shipped\", or when reporting the out…
Writing Unit Tests Use when writing or refactoring unit tests - a new test file, added cases, a flaky test, an unrea…