Software Engineering

Software-engineering work across the full development lifecycle: implementing changes, reviewing peers' code, debugging failures, and monitoring repository health. Use when (1) you've been handed a feature or bug to implement and need to write/branch/test/PR/merge end-to-end — load `Reference/writing-and-shipping-code.md`; (2) a PR has landed in your queue to review — load `Reference/reviewing-code.md`; (3) a test is failing, the build broke, or a bug was reported and you need to trace it to root cause — load `Reference/debugging-and-investigating.md`; (4) you're doing a routine repo health check, triaging stale PRs, or responding to CI/dependency alerts — load `Reference/monitoring-repositories.md`. Each phase doc has its own deeper Reference subdirectory with the specifics. For GitHub CLI mechanics (gh commands, repo cloning, PR/issue queries), use `using-github`. For Linear-based issue tracking, use `working-with-linear`. For drafting product specs before implementation, use `writing-product-specs`.