agentleFS
Sign inStart free
teslanikateslanika/pm-second-brain/skills/pm-spec/SKILL.md

pm-spec

Skill0 starsChanged 33 days agoMITView on GitHub

Builds a draft spec out of notes and decisions. Use when the user says "draft a spec", "pull the requirements together", "напиши спеку", "собери требования", or runs /pm-spec.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. ridwankustanto/mandor★ 2same name
    2. jpoindexter/theft-kit★ 1same 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

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If you find a contradiction, put it in the spec and mark it [verify].

    line 16
  2. Distinctive:

    Don't pick a side yourself.

    line 17
  3. Very specific:

    Read a closed topic (status: done) as history, not as current requirements.

    line 19
  4. Distinctive:

    Ask which feature the spec is for, if that isn't clear.

    line 23
  5. Very specific:

    Create a file in specs/:

    line 25
  6. Distinctive:

    Put a note at the top of the body: draft, needs review.

    line 44
  7. Very specific:

    Add the spec to index.md and to the "In progress" section of its topic.

    line 45
  8. Distinctive:

    Never write a claim without a source.

    line 49
  9. Distinctive:

    If the evidence is thin, write an open question rather than plausible text.

    line 51

≈ “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

Draft spec

Before you write

Find what the base already knows about the subject. In order: index.md, context/, the active topics in topics/, then decisions/ and specs/. If you find a contradiction, put it in the spec and mark it [verify]. Don't pick a side yourself.

Read a closed topic (status: done) as history, not as current requirements.

Steps

  1. Ask which feature the spec is for, if that isn't clear.
  2. Gather the sources: notes in calls/, decisions in decisions/.

  3. Create a file in specs/:

    ---
type: spec
date: 2026-09-19
source: calls/2026-09-19-sync.md
status: draft
---
  4. Fill in the sections:
    • Problem — what problem is being solved and whose it is.
    • In scope — the boundary of the work.
    • Out of scope — what is deliberately left out.
    • How we know it is done — checkable conditions.
    • Risks
    • Open questions — each with an owner or a next step.
    • Sources — [[file-name]] links to everything this grew from.
  5. Put a note at the top of the body: draft, needs review.
  6. Add the spec to index.md and to the "In progress" section of its topic.

Rules

  • Never write a claim without a source.
  • Mark an inference as one. Don't pass it off as the customer's words.
  • If the evidence is thin, write an open question rather than plausible text.

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