agentleFS
Sign inStart free
osrenosren/interview-flashcard/.github/skills/openspec-propose/SKILL.md

openspec-propose

Skill2 starsChanged 19 days agoNo licenceView on GitHub

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

166 other projects use a version of this, 126 of them edited; 31 new projects in the last 4 weeks, against 24 the 4 before.

Adopted by

Rising: 31 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.

Week of Sep 13: 7 new projectsWeek of Sep 20: 1 new projectWeek of Sep 27: 4 new projectsWeek of Oct 4: 12 new projectsWeek of Oct 11: 13 new projectsWeek of Oct 18: 6 new projectsWeek of Oct 25: 7 new projectsWeek of Nov 1: 5 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use source-command-opsx-apply, source-command-opsx-archive 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.
  • antech2-asyncSkill

    source-command-opsx-apply

    Implement tasks from an OpenSpec change (Experimental)

    Also in 5 projects that use this

  • antech2-asyncSkill

    source-command-opsx-archive

    Archive a completed change in the experimental workflow

    Also in 5 projects that use this

  • Microsoft AzureSkill

    openspec-update-change

    Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

    Also in 91 projects that use this

  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • goernSkill

    release-openspec

    Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.

    Also in 3 projects that use this

  • ElasticSkill

    openspec-verify-change

    Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

    Also in 40 projects that use this

  • +2 more from antech2-async
  • +2 more from goern

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. 5 are common, 7 are distinctive, and 8 are very specific to this project.

  • 5

    Common

    Most of the 126 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 8

    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 126 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