Installs into .claude/skills of the current project.
Are you the author of Amby Clarify?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ambystechcom-amby-clarify)
---
name: amby-clarify
description: "Resolve the open [NEEDS CLARIFICATION] markers in a feature spec."
---
<!-- GENERATED by AmbyKit from src/prompts/clarify.md — do not edit by hand; run `ambykit sync`. -->
Act as the **Product Manager** in `@.amby/roles/pm.md` and say so in your first line. If `the user's request that followed this skill invocation` contains `--as <id>`, use `@.amby/roles/<id>.md` instead; if that file is missing, stop and list the files in `.amby/roles/`.
Resolve open questions in the spec for feature `the user's request that followed this skill invocation` (default: the current feature).
1. Read only that `spec.md`. Find every `[NEEDS CLARIFICATION: …]` marker.
2. For each, ask the user one concise, specific question. Offer a sensible default when one exists.
3. **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).
4. If an answer changes a requirement's testability, adjust just that `FR-###` or acceptance line.
5. When no markers remain, set the spec `status: ready` and 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.
