agentleFS
45ck45ck/documentation-evidence-skills/.agents/skills/spec-writer/SKILL.md

spec-writer

Skill2 starsChanged 8 months agoMITView on GitHub

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-reviewer, code-reviewer and 1 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.
  • JeffallanSkill

    security-reviewer

    Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks. Produces vulnerability reports, prioritized recommendations, and compliance checklists.

    Also in 3 projects that use this

  • GoogleSkill

    code-reviewer

    Also in 4 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write structured specifications that turn intent into concrete, reviewable engineering artifacts.

    line 12
  2. Distinctive:

    Prefer structured, reusable artifacts over generic prose.

    line 49
  3. Distinctive:

    Do not fabricate evidence, references, or approval.

    line 55
  4. Distinctive:

    Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.

    line 56
  5. Distinctive:

    Do not leave identifiers or document links inconsistent.

    line 57
  6. Distinctive:

    Do not confuse “described” with “verified”.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 21 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

spec-writer

Purpose

Write structured specifications that turn intent into concrete, reviewable engineering artifacts.

Trigger this skill when

  • A durable documentation or evidence artifact is needed for review, submission, audit, or handover.
  • You need clearer linkage between requirements, design, testing, defects, decisions, or findings.
  • Existing documentation is fragmented, inconsistent, or weakly evidenced.

Expected inputs

  • problem statement
  • scope
  • requirements or notes
  • stakeholders if known

Deliverables

  • structured specification
  • open questions
  • acceptance criteria

Operating procedure

  1. Clarify the artifact boundary, audience, and review objective.
  2. Separate known facts from assumptions, placeholders, and missing evidence.
  3. Produce the skill-specific artifact in a form that can be reused directly.
  4. Link the result to upstream and downstream artifacts where helpful.
  5. Recommend the next best handoff instead of trying to do every document at once.

Quality gates

  • The output is specific to the current system, feature, or report context.
  • Identifiers, references, and labels are internally consistent.
  • Missing evidence or unresolved questions are made visible.
  • The result is directly usable in a repo, report, appendix, or review packet.

Handoff targets

  • design-rationale-writer
  • traceability-matrix-writer
  • reference-integrity-checker

Output style

  • Prefer structured, reusable artifacts over generic prose.
  • Make IDs, labels, references, and evidence explicit where possible.
  • Preserve traceability between related artifacts.
  • Surface missing evidence or unresolved questions instead of inventing closure.

Failure modes to avoid

  • Do not fabricate evidence, references, or approval.
  • Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.
  • Do not leave identifiers or document links inconsistent.
  • Do not confuse “described” with “verified”.

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.