agentleFS
Sign inStart free
thistleknotthistleknot/skills/speckit-specify/SKILL.md

speckit-specify

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Create or update the feature specification from a natural language feature description.

131 other projects use a version of this, 112 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use speckit-agent-context-update, speckit-git-commit 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.
  • Microsoft AzureSkill

    speckit-agent-context-update

    Refresh the managed Spec Kit section in coding agent context file(s)

    Also in 13 projects that use this

  • Sorcha-PlatformSkill

    speckit-git-commit

    Auto-commit changes after a Spec Kit command completes

    Also in 35 projects that use this

  • Sorcha-PlatformSkill

    speckit-git-feature

    Create a feature branch with sequential or timestamp numbering

    Also in 35 projects that use this

  • patterson-agentsSkill

    speckit-baseline

    Generate feature specifications by analyzing existing source code.

    Also in 3 projects that use this

  • patterson-agentsSkill

    claude-command-converter

    Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    agentic-workflows

    Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

    Also in 3 projects that use this

  • +3 more from Sorcha-Platform

The file

Show its rules and text

We split this skill into the rules it gives an agent

47 rules. 27 are common, 0 are distinctive, and 20 are very specific to this project.

  • 27

    Common

    Most of the 111 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 20

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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