spec-intake — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited spec-intake (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Turn a task from anywhere — a Jira/Linear ticket, a URL, a Slack message, a vague sentence — into one normalized spec, before any planning. Usable standalone, and the entry point of eskills:task-flow Phase 1.
paraphrase away a constraint.
few questions that change the work — before writing the spec, not after.
task-flow consumes next).## Objective
<one or two sentences: the outcome, in the user's terms>
## Acceptance criteria
- [ ] <observable, checkable condition>
- [ ] …
## Constraints
- <tech, data, deadline, compatibility, non-goals>
## Definition of done
- <tests, docs, review, deploy — what "finished" requires>
## Classification
- Project shape: greenfield | brownfield
- Hard-tech challenge: yes (algorithm / performance) | no200ms on N=10k" is.
task-flow: brownfield → feature-dev:code-explorer;hard-tech → the SPIKE sub-phase.
eskills:standards) — it's an internal doc.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.