Amby clarify
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.
npx -y skills add ambystechcom/AmbyKit --skill amby-clarifyAssembled 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
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.
SKILL.md
1.0 KB, as published. Nobody here has run it
<!-- GENERATED by AmbyKit from src/prompts/clarify.md — do not edit by hand; run `ambykit sync`. -->
Resolve open questions in the spec for feature the user's request that followed this skill invocation (default: the current feature).
- Read only that
spec.md. Find every[NEEDS CLARIFICATION: …]marker. - For each, ask the user one concise, specific question. Offer a sensible default when one exists.
- Edit only the affected line(s) — replace the marker with the resolved wording. Do not rewrite the rest of the file (token-frugal, non-destructive).
- If an answer changes a requirement's testability, adjust just that
FR-###or acceptance line. - When no markers remain, set the spec
status: readyand report a one-line summary.
Do not add scope. If the user raises new scope, note it as a new US-# rather than expanding others.