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.

workspace-setup

Install the workspace files that engineering-workflow skills depend on — the validation runbook (VALIDATION.md) that fix-loop reads, including whether changes land through pull requests or by direct push, and the issue-tracker record (ISSUE_TRACKER.md) that says where issues and work artifacts live — by copying bundled seed files into the workspace and fitting them to it from existing context, exploration, and a few easy-to-answer questions. Recommends an issue tracker from the evidence (such as the git remote), records the choice, and migrates open work that lives in committed markdown into that tracker, deleting the migrated files, unless the user chose repository files. Use when the user runs /workspace-setup, asks to set up or bootstrap the workflow in a repository, asks to move TODO, plan, or debt documents into the issue tracker, or when a skill such as fix-loop, bug-report, or work-once finds its workspace file missing. Re-running updates an existing install instead of overwriting it. Do not use for personal collaboration preferences (operator-setup).

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.