agentleFS
Sign inStart free
madebyarismadebyaris/spec-kit-command-cursor/.cursor/skills/sdd-audit/SKILL.md

sdd-audit

Skill198 starsChanged 5 months agoMITView on GitHub

Compare implementation against specifications, identify gaps and issues. Use for code review, quality assurance, and verifying spec compliance.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. khangpqvn/SDDADD★ 12same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Load specs: Read spec.md → plan.md → tasks.md

    line 18
  2. Very specific:

    Identify scope: Check todo-list.md for completed work

    line 19
  3. Distinctive:

    Use the ask question tool if audit criteria are unclear

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SDD Audit Skill

Compare implementations against specifications and generate structured review reports.

When to Use

  • Code review before marking tasks complete
  • Quality assurance checks
  • Verifying implementation matches spec

Workflow

  1. Load specs: Read spec.md → plan.md → tasks.md
  2. Identify scope: Check todo-list.md for completed work
  3. Inspect code: Review implementation for each task
  4. Gap analysis: Compare spec requirements vs actual code
  5. Generate report: Structured findings with severity levels

Audit Checklist

Reference references/checklist.md for the complete audit checklist.

Severity Levels

  • CRITICAL: Broken functionality, security risk, release blocker
  • MAJOR: Logic error, missing feature, significant bug
  • MINOR: Style issue, optimization opportunity, cleanup
  • OUTDATED: Code correct but spec needs updating

Report Format

## Audit Report: [Feature]

**Status:** Pass | Fail | Warnings

### Quick Stats
- CRITICAL: [N] | MAJOR: [N] | MINOR: [N]

### Review Comments
| ID | Severity | Location | Issue | Recommendation |

### Spec Compliance
| Requirement | Status | Evidence |

### Recommended Actions
1. [Priority action]

Integration

  • Works with sdd-verifier subagent for automated validation
  • Can trigger scripts/validate.sh for automated checks
  • Use the ask question tool if audit criteria are unclear

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free