Skip to content

sliekens/engineering-workflow

v2.12.0MIT

Engineering skills for issue backlog burn-down with runbook-driven validation and workspace setup, product mapping, build-failure diagnosis, complexity, consistency and conformance analysis, test design, scenario analysis, technical debt reviews, parallel change, yak-shave planning, capturing an unowned practice as a skill, one-step rabbit-hole teaching, and controlled technical writing.

hole

Teaches a person one step at a time, down a rabbit hole, and follows their signals. Use when they say teach me, explain this, go slowly, one thing at a time, /hole, or hole. Once a Hole lesson is already active, also use when they send clear, unclear, fuzzy, muddy, down, dig, surface, up, out, skip, lost, fork, tangent, wander, back, map, or go, and when a side path should return to the main path. A bare signal word does not start a lesson. Do not use when they asked you to implement, fix, finish, investigate, or audit the work. An ordinary go that approves a read-only investigation is not this skill.

Read SKILL.md at the source

Pinned to revision 152627988e4b, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.