A refactoring assistant for changing existing code structure while following documented strategies. It covers both tactical changes for everyday work and strategic changes to architecture, the high-level design of a system.
A release assistant for preparing and publishing software versions. It covers release subcommands, version types, workflows, and rules for increasing version numbers.
A guided team retrospective for reviewing a Sprint, a time-boxed period of development, or a Release, a published version of a product. It helps identify improvements and track follow-up actions.
A reverse-engineering assistant for examining existing software and understanding how it works. The description mentions three analysis dimensions, subcommands, and a full-analysis mode.
A guide for writing, maintaining, practising, and reviewing runbooks. A runbook is a step-by-step operations procedure used by the people responsible for running a service.
A guide for automated security checks covering software dependencies, known CVEs, exposed secrets, and licence compliance. CVEs are public records of known security vulnerabilities.
A guide for turning a repeatable development process into a coding-agent skill. It covers when to use the skill, its core principles, decision-making, and where to place it.
A guide to choosing service indicators, setting service objectives, and managing an error budget. An SLI measures service quality, an SLO states the target, and an error budget is the allowed amount of failure.
A generator for additional development documents from an approved software design specification. BDD describes expected behaviour as scenarios, TDD starts with tests, and ATDD records acceptance checks.
Definitions and decision guidance for a software design specification process, including its format, states, and change operations. The description says lifecycle enforcement now belongs to a separate adoption layer.