Amby clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.From its SKILL.md
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.
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.
SKILL.md
1.0 KB, 212 tokens by cl100k_base, 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.