agentsclimarketplace
Sign in

Convex feature spec

Skill BjornMelin/dev-skills/skills/convex-feature-spec

Convex-first specs—model, API, rollout, verify. New Convex plans. Not backend audit (convex-audit).From its SKILL.md

Install
npx -y skills add BjornMelin/dev-skills --skill convex-feature-spec

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, as published. Nobody here has run it

Convex Feature Spec

Use this skill for green-field or breaking-change-tolerant feature planning where the output is a complete implementation spec.

Workflow

  1. Read the repo AGENTS.md.
  2. Run ~/.codex/skill-support/bin/convex-scan inventory --cwd <repo> --out <json> to ground the current backend surface.
  3. Read references/feature-spec.md.
  4. Read references/components.md if the feature may use existing Convex components or reusable backend patterns.
  5. Read references/rollout-and-migration.md before finalizing any spec that changes schema, auth, or rollout order.
  6. Research the active APIs before locking any non-trivial design.
  7. Output an implementation-ready spec with task order, interfaces, risks, and verification.

Use When

  • The user asks for a new feature spec, a Convex-first architecture plan, or a complete backend-driven design.
  • The repo uses Convex and the planning output must include schema and function contracts.

Do Not Use When

  • The task is reviewing or fixing the current implementation.
  • The task is just docs alignment or dependency work.

Outputs

  • feature objective
  • schema and function contract changes
  • rollout and migration plan
  • ordered implementation and verification steps

What ships with it: 5 files

2.1 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Gives 0 of the 12 instructions most product spec skills give

Counted across 483 of the 502 authors here whose files we hold, read 2026-09-06

  • Write the PRD using the templatein 39 of 483, across 36 files
  • Ask one question at a timein 24 of 483
  • Write acceptance criteria in Given-When-Then formatin 24 of 483
  • Write user stories with acceptance criteriain 22 of 483, across 21 files
  • Respect ADRs in areas you touchin 21 of 483, across 17 files
  • Use the domain glossary vocabulary throughout the PRDin 20 of 483, across 16 files
  • Explore the repo to understand the current codebasein 19 of 483, across 15 files
  • Provide testable acceptance criteriain 19 of 483, across 17 files
  • Publish the PRD to the issue trackerin 18 of 483, across 14 files
  • Apply the ready-for-agent triage labelin 15 of 483, across 13 files
  • Prefer existing seams over new onesin 14 of 483, across 12 files
  • Save the PRD as a markdown filein 14 of 483, across 9 files

Said here and by no other author read

  • read the repository's AGENTS.md
  • run convex-scan inventory to ground the backend surface
  • read the components reference when reusing existing components
  • read the rollout reference before any schema or auth change
  • research active APIs before locking non-trivial design
  • output an implementation-ready spec

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,045. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.