Skip to content

sliekens/engineering-workflow

v2.16.0MIT

Engineering skills for issue backlog burn-down with runbook-driven validation, bug reports, one-issue wakes that resume from the issue tracker, 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, whole-codebase untangling, capturing an unowned practice as a skill built from a catalog of primitives, one-step rabbit-hole teaching, and controlled technical writing.

duh

Before a choice-like turn, drop every option a recorded lock, the code, or a wait already decides. Continue when one option remains. Use on every choice-like turn where the answer might be obvious. That includes a turn that offers a choice, ranks options, or is about to end on a question. Also use when grill-me is about to ask, or when fix-loop is about to treat a choice as the user's. Do not use to interview the user (grill-me). Do not use to fix an issue (fix-loop). Do not use to write a Decision fork: line. That line is the parent's job after this skill returns ask.

Read SKILL.md at the source

Pinned to revision 59ea847bc601, 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.