agentleFS
mmaripanguecmmaripanguec/dev-sdd-kit/.claude/skills/spec-review/SKILL.md

spec-review

Skill2 starsChanged 4 months agoMITView on GitHub

Validates a spec against the factory's Definition of Ready. Use before the DoR gate or when asked to "review spec".

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use get-pr-reviews, push-everything and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • saffron-healthSkill

    get-pr-reviews

    Get nicely formatted output of the last review comments on a PR. Used internally by other skills.

    Also in 3 projects that use this

  • saffron-healthSkill

    push-everything

    Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

    Also in 3 projects that use this

  • NVIDIASkill

    generate-spec

    Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.

    Also in 3 projects that use this

  • telefrekSkill

    spec-init

    Bootstrap the spec corpus for this project

    Also in 3 projects that use this

  • AWSSkill

    implement-spec

    Implement the result of /to-spec and /to-tickets in code.

    Also in 8 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 3 projects that use this

  • +2 more from saffron-health

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 2

    Distinctive

    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:

    EVERY acceptance criterion is verifiable Gherkin (observable and measurable outcome.

    line 14
  2. Distinctive:

    No secrets, credentials or real customer data in the document.

    line 22
  3. Very specific:

    No pending [NEEDS CLARIFICATION] markers (resolve with /clarify.

    line 23
  4. Distinctive:

    Do not edit the spec: report.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “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

Review spec $ARGUMENTS against this Definition of Ready. For each point: PASS / FAIL + evidence (cite the line) or what is missing.

The factory's DoR

  1. Problem and goal in business language, with no implicit technical solution.
  2. Stories meet INVEST; none estimated > 8 points without splitting.
  3. EVERY acceptance criterion is verifiable Gherkin (observable and measurable outcome; no "must be robust/fast/friendly").
  4. Out of scope explicit and non-empty.
  5. Edge cases enumerated (nulls, concurrency, third-party errors, permissions).
  6. Business rules numbered and consistent with knowledge/business-rules.md.
  7. Dependencies and assumptions listed; blockers marked.
  8. Regulatory/personal-data requirements identified where applicable.
  9. NFRs with numbers (SLO, latency, volume), not adjectives.
  10. No secrets, credentials or real customer data in the document.
  11. No pending [NEEDS CLARIFICATION] markers (resolve with /clarify; the decisions are recorded in the Clarifications section).
  12. SC-xx success criteria measurable and technology-agnostic (threshold and deadline; certifiable in F7 and checkable against knowledge/usage.md).
  13. Stories prioritized [P1]/[P2]/[P3]; the P1s on their own constitute a viable and independently testable MVP.

Complement: the CROSS-consistency with business rules, ADRs, as-is and task plan is audited by /consistency; recommend it if it has not been run yet.

Final verdict: READY FOR DoR / NEEDS CHANGES (prioritized list). Do not edit the spec: report; changes are applied by the create-review-improve cycle.

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.