AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Specsmith Audit

skill-layer1labs-specsmith-specsmith-audit · by layer1labs

Run specsmith audit to check for governance drift between requirements, tests, and architecture. Required before advancing an AEE phase.

↗ Website ↗ Repository
— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-layer1labs-specsmith-specsmith-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Specsmith Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Specsmith Audit

Checks the project for drift between requirements (ARCHITECTURE.md), test cases, and the codebase. Must pass before advancing an AEE phase.

How to run

specsmith audit

Interpreting results

29 PASS   ← all requirements have matching tests and implementation
 2 WARN   ← drift detected — investigate these
 0 FAIL

All items must be PASS or suppressed before specsmith phase advance.

When a WARN appears

  1. Read the warning — it references a requirement ID (e.g. R20) and describes what's missing
  2. Fix it: add the missing test, update ARCHITECTURE.md, or implement the requirement
  3. Re-run specsmith audit to confirm it passes
  4. If it's a confirmed false positive: specsmith audit --suppress

Suppressing a false positive

Only suppress if you've verified the requirement IS met but the audit can't detect it:

specsmith audit --suppress SEAL-XXXX-001

Suppressions are permanent — use sparingly.

Common causes of WARN

  • Requirement in ARCHITECTURE.md has no corresponding test case
  • Test exists but requirement ID reference is missing from the test
  • Implementation exists but the architecture doc wasn't updated to match

After fixing all warnings

specsmith audit          # confirm all pass
specsmith phase advance  # advance the phase
specsmith save           # commit the phase bump

Quick audit before a session

Run specsmith audit at the start of a session to catch drift from the previous session before making new changes.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML