security-standard
Installation
SKILL.md
Security Standard
The technical spec's security file is the design: its threat model and its
SEC-NN controls. The review checklist checks each control in each PR. This
document is the audit view: it takes the standard risk lists and shows, row by
row, what the project does and where. A reader checks a row by opening its
file. A row with no file is only a claim.
1. Read
- Controls. The security file in
docs/technical-specs/(usually07-security.md) and itsSEC-NNIDs. If the spec has no control IDs, stop and ask the user to runtechnical-specfor that section first. - Code. The auth, validation, rate-limit, header, logging, and secrets code the controls name. Read the code; do not trust the spec's description of it.
- Delivery.
.github/workflows/,.github/dependabot.yml, the lockfile,Dockerfile, anddocs/deployment-plan/. - Existing document. If the project already has a security standard in its own layout, it is the source of truth. Update it in that layout.