Skip to content

sliekens/engineering-workflow

v2.15.1MIT

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.

bug-report

File one reported defect as an issue in the workspace issue tracker, with expected behavior, actual behavior, a repro or an explicit none, and evidence as identifiers rather than log or trace payloads. Use when the user reports a bug, says something is broken, or asks to file or write a bug report, and that defect is not already an issue, including a defect backlog routes here. Search open issues first and stop when one states the same actual behavior. Stop when the new issue exists. Do not fix it (fix-loop). When the issue-tracker record is missing, stop and use workspace-setup. When work-once is the caller, return the stop record and do not write the cursor. Do not use for a structural-debt inventory with no failing behavior (technical-debt-audit), or to diagnose an intermittent build (flaky-build-investigation).

Read SKILL.md at the source

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