enocgit

address-review

Triages review comments on an open pull request — from humans and from bots (CodeRabbit, bugbot, Codex, Sourcery, …) — and addresses them. Reads every comment, verifies and challenges each one against the code, the frozen contract, and the ADRs to weed out false positives, then auto-fixes the trivial and gates the rest behind a plan. Manually invoked, standalone — not tied to a pipeline stage. Use when the user says "address the PR reviews", "go through CodeRabbit's comments", "handle the bugbot findings", "handle the codex findings" or "respond to the review".

feature-start

Starts implementation of one decomposed task: isolates a workspace (a feature branch by default; a git worktree only when isolation is critical), loads the relevant PRD, ADR, and frozen contract into context, then enters plan mode and proposes a per-task plan for approval before any code is written. Use at the start of Stage 4 (Implement) once scope is approved, or when the user says "start working on issue #N", "begin this task", or "let's implement {feature}".

sdlc

Orchestrates an end-to-end, plan-gated software build pipeline: routes each stage to the right skill while enforcing human approval gates. Covers discovery, PRD, stress-test, architecture, API contracts, decomposition, implementation, QA, review, landing, and retro. The single entry point for the workflow. Use when the user wants to build a feature or product the disciplined way, start or resume structured development, asks "what stage are we at" / "what's next", or says "start the sdlc" / "run the pipeline".

Code & Development Listed

definition-of-done-review

Reviews a change against this team's Definition of Done before merge — beyond generic code review — checking acceptance criteria, contract fidelity, test coverage at the right layer, docs/ADR updates, and security for sensitive areas, then gives a pass/fail verdict with file:line evidence. Use at Stage 6 after code-review and simplify, or when the user asks "is this ready to merge" or "run the DoD check".

project-status

Reports where the project stands by reading the live tracker (GitHub Issues/Projects) and summarizing it — read-only against external trackers, while local-only mode maintains docs/progress.md as the tracker itself. Use when the user asks "what's the project status", "where are we on {epic}", "what's next", or wants a Now/Next/Blocked view; also to disclose the breakdown after Decompose (Stage 3) or the state after landing a PR (Stage 7).