speq-record — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited speq-record (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.
This skill is a thin orchestrator. It verifies preconditions and delegates the deterministic merge work to the recorder-agent sub-agent. Recording is mechanical file surgery and does not need deep reasoning.
Invoke before starting:
/speq-cli — Spec validationThe recorder-agent sub-agent invokes /speq-code-tools, /speq-cli, and /speq-git-discipline itself.
Get plan name from user prompt. If none specified, use AskUserQuestion to present a list of plans under specs/_plans/.
Check: specs/_plans/<plan-name>/verification-report.md exists?
├─ Yes → Proceed
└─ No → STOP: "Run /speq-implement <plan-name> first."Spawn the recorder sub-agent with the plan name:
Task(
subagent_type="recorder-agent",
description="Record <plan-name> into permanent specs",
prompt="""
## Plan Name
<plan-name>
## Context
- Verification report confirmed at: specs/_plans/<plan-name>/verification-report.md
- Plan file: specs/_plans/<plan-name>/plan.md
- Delta specs: specs/_plans/<plan-name>/**/spec.md
## Your Task
Merge all delta specs into permanent specs per the `recorder-agent` workflow.
Validate between merges. Archive the plan on success. If any library threshold
is exceeded (scenarios > 10, domain features > 8), STOP before archiving and
return a question for the user.
Return a summary of merged features and the archive path.
"""
)If the sub-agent returns threshold signals:
AskUserQuestion to gather user's organizational decisionrecorder-agent with the decision, OR apply a small edit directly if the action is trivial (e.g., rename a file)Report to user:
✓ Verification report confirmed
✓ All deltas merged
✓ Spec library validated
✓ Plan archived: specs/_recorded/YYYY-MM-DD-<plan-name>| Step | Performed by | Why |
|---|---|---|
| Precondition checks, user questions | This skill (pins Sonnet) | Lightweight orchestration |
| Delta merge, validation, archive | recorder-agent sub-agent | Mechanical file surgery |
Keeping orchestrator and sub-agent separate preserves the rotation discipline: if the spec library is very large, the sub-agent can be re-spawned with a fresh context without losing orchestration state.
| Pattern | Why Wrong |
|---|---|
| Record without verification report | Implementation not proven |
| Orchestrator merges directly | Breaks rotation / context discipline |
| Assume split/domain decisions | User must confirm |
| Skip validation | Broken specs may result |
| Leave DELTA markers | Pollutes permanent specs |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.