skillboardUpdated every 6 hours
skillboardKeeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Spec Driven Development Specs live in . They are the source of truth for architectural decisions, API contracts, and implementation scope. Implementation and specs must stay in sync — neither leads exclusively. Core Loop Before Starting Work 1. Find the spec. Search for files matching the feature: 2. Read the full spec. Understand scope, decisions, API contracts, and open questions before writing code. 3. If no spec exists and the task is non trivial (new module, new API, architectural change),…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/spec-driven-development · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/spec-driven-development"
cp -r ".agents/skills/spec-driven-development" ".claude/skills/spec-driven-development"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.