adv-sql

Use when extracting reusable workflow patterns, debugging lessons, or project-specific operating knowledge from completed work in this repository.

Use when capturing or checking a repository workflow checkpoint before a risky change, after a milestone, or during a design-to-implementation handoff.

Use when defining or revising repository architecture, design documents, concept boundaries, or cross-document relationships before implementation.

Use when defining or checking acceptance criteria, release readiness, or completion evidence for a repository change or feature.

Use when executing a confirmed repository plan or task and writing code that must stay within documented scope and project conventions.

Use when checking or updating the repository's `.claude/index.yaml` so design, plan, and task relationships stay internally consistent.

Use when a confirmed design or multi-step requirement needs to be broken into repository-local plans and tasks before implementation.

Use when reviewing repository changes for behavioral correctness, design consistency, quality risks, or verification gaps before considering the work complete.

Use when the user wants a concise repository workflow status summary covering design docs, plans, tasks, index health, and git state.

Use when implementing or changing behavior in this repository and you need to drive the work through deliberate pytest-first development.

Use when working with a repository or personal knowledge vault built from Markdown notes, wikilinks, and searchable note metadata.

Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.

Memory Vault MCP server — Markdown + SQLite knowledge store with bidirectional [[wikilinks]]. Use when the user wants to create, read, edit, search, or manage interconnected knowledge notes. Provides 11 tools: vault_write, vault_write_batch, vault_read, vault_edit, vault_delete, vault_rename, vault_list, vault_search, vault_backlinks, vault_traverse, vault_lint.