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.

work-once

Run one skill for one issue, write the returned next skill onto that issue, and exit. Use when a schedule wakes an agent, when the user runs /work-once, or when one tick should resume from the issue tracker. Prefer an open issue that already has next_skill and is not waiting on a person; a person unblocks those with backlog, which this skill never runs. Otherwise run fix-loop on the oldest actionable issue, one issue only. Do not load the returned next skill in this run. Do not use to burn down a backlog in one sitting (fix-loop), to plan a replacement (yak-shave), to perform parallel change (expand-and-contract), or to file a defect (bug-report), except as the single skill this tick was told to run.

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.