agentsclimarketplace

Amby specify

Skill ambystechcom/AmbyKit/.agents/skills/amby-specify

Spec-Driven Development framework that helps AI coding assistants build better software — author your specs, user stories, UI design, plans and tasks once, and emit native config for Claude Code, OpenCode, GitHub Copilot, Cursor, Antigravity and more.

Install
npx -y skills add ambystechcom/AmbyKit --skill amby-specify

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

  • 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.

SKILL.md

1.3 KB, as published. Nobody here has run it

<!-- GENERATED by AmbyKit from src/prompts/specify.md — do not edit by hand; run `ambykit sync`. -->

Write a specification for: the user's request that followed this skill invocation

Context: read @.amby/constitution.md and the structure of @.amby/templates/spec.md only. Do not read other specs.

  1. Create the feature dir specs/NNN-slug/ (next number, kebab-slug from the title) and write spec.md following @.amby/templates/spec.md.
  2. Define user stories (US-#): role / capability / benefit, a priority (P1/P2/P3), why that priority, an independent-test statement, and depends-on/blocked-by if any. Set status: draft.
  3. Write acceptance criteria in Given/When/Then per story.
  4. Write functional requirements (FR-###) in EARS notation (SHALL / WHEN / WHILE / IF-THEN / WHERE). Each must be testable.
  5. Write measurable, tech-agnostic success criteria (SC-###).
  6. Capture WHAT/WHY only — no technology choices. Flag every unknown inline as [NEEDS CLARIFICATION: …] instead of guessing.

Keep it tight. Reference the constitution by principle number where relevant; don't restate it.

Keep looking

Skills are one crate of 328,083. 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.