Amby specify

Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.From its SKILL.md

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.

One thing to look at

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.

1.3 KB, 310 tokens by cl100k_base, as published. Nobody here has run it

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.

Create the feature dir specs/NNN-slug/ (next number, kebab-slug from the title) and write spec.md following @.amby/templates/spec.md.
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.
Write acceptance criteria in Given/When/Then per story.
Write functional requirements (FR-###) in EARS notation (SHALL / WHEN / WHILE / IF-THEN / WHERE). Each must be testable.
Write measurable, tech-agnostic success criteria (SC-###).
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.

Read from the repository

Just SKILL.md. No reference files, no scripts.