agents-mdAudit, write, split, or wire up global and repo-level AGENTS.md, CLAUDE.md, GEMINI.md, and .github/copilot-instructions.md. Enforces the 5-layer context hierarchy, the 6-step placement sieve (personal vs. team vs. repo vs. tooling vs. session state), the <150-line repo budget, and thin tool-pointer
decision-captureMid-session decision-to-spec-commit workflow. Invoke as soon as a design decision is reached in conversation (a scope choice, schema change, source-of-truth ruling, naming convention, or any "we decided X, not Y" moment) -- not at session end. Writes/amends the repo's spec/decision documentation to
doc-review-commandsBring a repo's documentation back in sync with its code: README, CHANGELOG, CLAUDE.md/AGENTS.md and SDD specs (requirements, design, tasks). Includes a doc-health analyzer, focused update workflows (core docs, SDD artifacts, quick edits) and a pre-commit documentation QA pass. Use when the user says
plan-docPlan-first workflow for multi-item change batches. Before executing any batch of related changes (review-driven fixes, a refactor, doc restructuring, multi-file feature work), write a plan document into the repo's specs/ (or docs/) directory, commit it on its own, THEN execute commit-by-commit again
python-lint-fixCheck that a Python repo's lint and format tooling is ready (uv, pre-commit and its git hook, .pre-commit-config.yaml, markdownlint version) and run pre-commit across the repo on demand. Use when the user asks to lint or format the repo, run ruff/mdformat/markdownlint, set up or install pre-commit h
sdd-git-commitCommit workflow for Spec-Driven Development repos: checks the diff for secrets and junk files, keeps specs, the task list, the session pointer and the CHANGELOG in step with the code, then writes a Conventional Commits message. Use whenever the user asks to commit, "commit this", "make a commit", "c
sdd-project-initScaffold a new non-Python project (Go, TypeScript, Bash, Rust, docs-only, any stack) with Spec-Driven Development structure: AGENTS.md with SDD gates, README, .gitignore, specs/requirements.md, design.md, tasks.md and a feature template. Use when the user wants to start, bootstrap, init or scaffold
session-closeSession end-of-work checklist. Refreshes the repo's durable "what's next" pointer file (e.g. specs/NEXT.md) so a future session can resume without re-discovering state, checks for uncommitted work, and gets explicit human sign-off on the content before ending. Use when the user says "close session",
ste-procedureWrite or revise step-by-step operational procedures (MOPs, runbooks, change and maintenance procedures, SOPs, rollback plans) in Simplified Technical English style based on ASD-STE100. Use when asked to write a MOP, runbook, change procedure, cutover or rollback plan, or to make a procedure clearer.