Distil reusable engineering rules from code changes and record them in docs/rules/. Use whenever the user wants to extract rules, conventions, or lessons from a diff, a commit, or the current uncommitted changes — e.g. "extract the rule from these changes",…
Read-only cross-artifact consistency check across spec.md, plan.md, and tasks.md. Detects gaps, conflicts, and FRAMEWORK.md violations before implementation begins.
Create a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
Generate a dependency-ordered, phase-based task list from spec.md and plan.md. Run after spec-kit-plan and before spec-kit-analyse.
Use this skill when creating, reviewing, or migrating relational database schemas. It applies across projects and ORMs/frameworks such as Symfony Doctrine, Prisma, Drizzle, Rails ActiveRecord, Laravel Eloquent, raw SQL, or any other relational database layer.
Diagnose database issues via SQL row counts without seeing actual data values. Use when debugging missing or incorrect database data, 500 errors traced to queries, or data integrity issues where the user runs SQL and reports only row counts back.
Use the IDE AskQuestion tool when the agent needs user input. Use when asking the user to choose between options, confirm a decision, or pick from discovered alternatives — never ask multiple-choice questions in plain chat.
Enforce semantic line breaks in Markdown specification prose. Use this whenever creating or editing specs, requirements, ADRs, README-style specification docs, or Markdown under specs/ or docs/, especially when paragraphs would otherwise be written as long…