[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SEA1RKPM52J0BAW8DMAFX":3,"skill-same:01M72SEA1RKPM52J0BAW8DMAFX":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M72SEA1RKPM52J0BAW8DMAFX","speckit-clarify",null,"Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.","EHotwagner\u002FFS-Skia-UI","EHotwagner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1645484?v=4","01M72S7CTBDPQDQHQJKKHY87K9","01M72S7CVFD0JN82RVX21NFEVC",2,"MIT","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-clarify\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: \"speckit-clarify\"\ndescription: \"Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fcommands\u002Fclarify.md\"\n---\n\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before clarification)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.before_clarify` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.before_clarify` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n\n    Wait for the result of the hook command before proceeding to the Outline.\n    ```\n\n## Outline\n\nGoal: Detect and reduce ambiguity or missing decision points in the active feature specification, recording clarifications directly in the spec file.\n\nNote: This workflow is expected to run and complete BEFORE invoking `\u002Fspeckit-plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.\n\nExecution steps:\n\n1. Run `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode \u002F `-Json -PathsOnly`). Parse minimal JSON payload fields:\n   - `FEATURE_DIR`\n   - `FEATURE_SPEC`\n   - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)\n   - If JSON parsing fails, abort and instruct user to re-run `\u002Fspeckit-specify` or verify feature branch environment.\n   - For single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n1a. **Source-spec pre-check (consult before asking).** If a `source-spec.md`\n   snapshot exists in `FEATURE_DIR`, load and read it **before forming any\n   clarification questions**. Treat it as authoritative context for what the\n   feature already resolves: do **not** ask a question whose answer the\n   snapshot already settles, and let it sharpen the remaining genuinely-open\n   questions. When no `source-spec.md` is present in `FEATURE_DIR`, this step\n   is a silent **no-op** — proceed exactly as you would otherwise (graceful\n   degradation; the absence is not an error and produces no output).\n\n2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy, marking each category Clear \u002F Partial \u002F Missing. Produce an internal coverage map for prioritization (do not output the raw map unless no questions will be asked).\n\n   Functional Scope & Behavior:\n   - Core user goals & success criteria\n   - Explicit out-of-scope declarations\n   - User roles \u002F personas differentiation\n\n   Domain & Data Model:\n   - Entities, attributes, relationships\n   - Identity & uniqueness rules\n   - Lifecycle\u002Fstate transitions\n   - Data volume \u002F scale assumptions\n\n   Interaction & UX Flow:\n   - Critical user journeys \u002F sequences\n   - Error\u002Fempty\u002Floading states\n   - Accessibility or localization notes\n\n   Non-Functional Quality Attributes:\n   - Performance (latency, throughput targets)\n   - Scalability (horizontal\u002Fvertical, limits)\n   - Reliability & availability (uptime, recovery expectations)\n   - Observability (logging, metrics, tracing signals)\n   - Security & privacy (authN\u002FZ, data protection, threat assumptions)\n   - Compliance \u002F regulatory constraints (if any)\n\n   Integration & External Dependencies:\n   - External services\u002FAPIs and failure modes\n   - Data import\u002Fexport formats\n   - Protocol\u002Fversioning assumptions\n\n   Edge Cases & Failure Handling:\n   - Negative scenarios\n   - Rate limiting \u002F throttling\n   - Conflict resolution (e.g., concurrent edits)\n\n   Constraints & Tradeoffs:\n   - Technical constraints (language, storage, hosting)\n   - Explicit tradeoffs or rejected alternatives\n\n   Terminology & Consistency:\n   - Canonical glossary terms\n   - Avoided synonyms \u002F deprecated terms\n\n   Completion Signals:\n   - Acceptance criteria testability\n   - Measurable Definition of Done style indicators\n\n   Misc \u002F Placeholders:\n   - TODO markers \u002F unresolved decisions\n   - Ambiguous adjectives (\"robust\", \"intuitive\") lacking quantification\n\n   For each category with Partial or Missing status, add a candidate question opportunity unless:\n   - Clarification would not materially change implementation or validation strategy\n   - Information is better deferred to planning phase (note internally)\n\n3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:\n    - Maximum of 5 total questions across the whole session.\n    - Each question must be answerable with EITHER:\n       - A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR\n       - A one-word \u002F short‑phrase answer (explicitly constrain: \"Answer in \u003C=5 words\").\n    - Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.\n    - Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.\n    - Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness).\n    - Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests.\n    - If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic.\n\n4. Sequential questioning loop (interactive):\n    - Present EXACTLY ONE question at a time.\n    - For multiple‑choice questions:\n       - **Analyze all options** and determine the **most suitable option** based on:\n          - Best practices for the project type\n          - Common patterns in similar implementations\n          - Risk reduction (security, performance, maintainability)\n          - Alignment with any explicit project goals or constraints visible in the spec\n       - Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).\n       - Format as: `**Recommended:** Option [X] - \u003Creasoning>`\n       - Then render all options as a Markdown table:\n\n       | Option | Description |\n       |--------|-------------|\n       | A | \u003COption A description> |\n       | B | \u003COption B description> |\n       | C | \u003COption C description> (add D\u002FE as needed up to 5) |\n       | Short | Provide a different short answer (\u003C=5 words) (Include only if free-form alternative is appropriate) |\n\n       - After the table, add: `You can reply with the option letter (e.g., \"A\"), accept the recommendation by saying \"yes\" or \"recommended\", or provide your own short answer.`\n    - For short‑answer style (no meaningful discrete options):\n       - Provide your **suggested answer** based on best practices and context.\n       - Format as: `**Suggested:** \u003Cyour proposed answer> - \u003Cbrief reasoning>`\n       - Then output: `Format: Short answer (\u003C=5 words). You can accept the suggestion by saying \"yes\" or \"suggested\", or provide your own answer.`\n    - After the user answers:\n       - If the user replies \"yes\", \"recommended\", or \"suggested\", use your previously stated recommendation\u002Fsuggestion as the answer.\n       - Otherwise, validate the answer maps to one option or fits the \u003C=5 word constraint.\n       - If ambiguous, ask for a quick disambiguation (still the same question; do not advance).\n       - Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.\n    - Stop asking further questions when:\n       - All critical ambiguities resolved early (remaining queued items become unnecessary), OR\n       - User signals completion (\"done\", \"good\", \"no more\"), OR\n       - You reach 5 asked questions.\n    - Never reveal future queued questions in advance.\n    - If no valid questions exist at start, immediately report no critical ambiguities.\n\n5. Integration after EACH accepted answer (incremental update):\n    - Maintain an in-memory representation of the spec (loaded once at start) plus the raw file contents.\n    - For the first integrated answer this session: ensure a `## Clarifications` section exists (create it just after the highest-level contextual\u002Foverview section per the spec template if missing), and under it create a `### Session YYYY-MM-DD` subheading for today if not present.\n    - Append a bullet immediately after acceptance: `- Q: \u003Cquestion> → A: \u003Cfinal answer>`.\n    - Then immediately apply the clarification to the most appropriate section(s):\n       - Functional ambiguity → Update or add a bullet in Functional Requirements.\n       - User interaction \u002F actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.\n       - Data shape \u002F entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.\n       - Non-functional constraint → Add\u002Fmodify measurable criteria in Success Criteria > Measurable Outcomes (convert vague adjective to metric or explicit target).\n       - Edge case \u002F negative flow → Add a new bullet under Edge Cases \u002F Error Handling (or create such subsection if template provides placeholder for it).\n       - Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as \"X\")` once.\n    - If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.\n    - Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).\n    - Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.\n    - Keep each inserted clarification minimal and testable (avoid narrative drift).\n\n6. Validation (performed after EACH write plus final pass):\n   - Clarifications session contains exactly one bullet per accepted answer (no duplicates).\n   - Total asked (accepted) questions ≤ 5.\n   - Updated sections contain no lingering vague placeholders the new answer was meant to resolve.\n   - No contradictory earlier statement remains (scan for now-invalid alternative choices removed).\n   - Markdown structure valid; only allowed new headings: `## Clarifications`, `### Session YYYY-MM-DD`.\n   - Terminology consistency: same canonical term used across all updated sections.\n\n7. Write the updated spec back to `FEATURE_SPEC`.\n\n8. Report completion (after questioning loop ends or early termination):\n   - Number of questions asked & answered.\n   - Path to updated spec.\n   - Sections touched (list names).\n   - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial\u002FMissing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial\u002FMissing but low impact).\n   - If any Outstanding or Deferred remain, recommend whether to proceed to `\u002Fspeckit-plan` or run `\u002Fspeckit-clarify` again later post-plan.\n   - Suggested next command.\n\nBehavior rules:\n\n- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: \"No critical ambiguities detected worth formal clarification.\" and suggest proceeding.\n- If spec file missing, instruct user to run `\u002Fspeckit-specify` first (do not create a new spec here).\n- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).\n- Avoid speculative tech stack questions unless the absence blocks functional clarity.\n- Respect user early termination signals (\"stop\", \"done\", \"proceed\").\n- If no questions asked due to full coverage, output a compact coverage summary (all categories Clear) then suggest advancing.\n- If quota reached with unresolved high-impact categories remaining, explicitly flag them under Deferred with rationale.\n\nContext for prioritization: $ARGUMENTS\n\n## Post-Execution Checks\n\n**Check for extension hooks (after clarification)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.after_clarify` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.after_clarify` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs on phase completion.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - **Hook execution precedence** (D1): when `settings.auto_execute_hooks: true` in `.specify\u002Fextensions.yml`, a **mandatory** hook (`optional: false`) **auto-runs** with no confirmation; an **optional** hook (`optional: true`) is **always surfaced** (\"To execute: `\u002F{command}`\") and is **never force-run** by `auto_execute_hooks`; a hook with a non-empty `condition` is **never** evaluated by this skill — evaluation is left to the executor and the notice reports the resolved decision. When `auto_execute_hooks: false`, even mandatory hooks are surfaced for confirmation.\n  - **Effective-hooks notice** (D2): after the merge + dedup by `(extension, command)`, emit **one** consolidated notice for the phase so the operator never hand-reconciles files — the promoted feedback hook (`optional: false`) appears as `auto-run`, never as a surfaced optional:\n    ```\n    ## Effective hooks for clarify\n    - {extension}:{command} — auto-run        (mandatory; auto_execute_hooks=true)\n    - {extension}:{command} — surfaced        (optional)\n    - {extension}:{command} — skipped         (enabled: false)\n    - {extension}:{command} — condition-deferred\n    ```\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    ```\n","## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before clarification)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.before_clarify` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.before_clarify` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n\n    Wait for the result of the hook command before proceeding to the Outline.\n    ```\n\n## Outline\n\nGoal: Detect and reduce ambiguity or missing decision points in the active feature specification, recording clarifications directly in the spec file.\n\nNote: This workflow is expected to run and complete BEFORE invoking `\u002Fspeckit-plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.\n\nExecution steps:\n\n1. Run `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode \u002F `-Json -PathsOnly`). Parse minimal JSON payload fields:\n   - `FEATURE_DIR`\n   - `FEATURE_SPEC`\n   - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)\n   - If JSON parsing fails, abort and instruct user to re-run `\u002Fspeckit-specify` or verify feature branch environment.\n   - For single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n1a. **Source-spec pre-check (consult before asking).** If a `source-spec.md`\n   snapshot exists in `FEATURE_DIR`, load and read it **before forming any\n   clarification questions**. Treat it as authoritative context for what the\n   feature already resolves: do **not** ask a question whose answer the\n   snapshot already settles, and let it sharpen the remaining genuinely-open\n   questions. When no `source-spec.md` is present in `FEATURE_DIR`, this step\n   is a silent **no-op** — proceed exactly as you would otherwise (graceful\n   degradation; the absence is not an error and produces no output).\n\n2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy, marking each category Clear \u002F Partial \u002F Missing. Produce an internal coverage map for prioritization (do not output the raw map unless no questions will be asked).\n\n   Functional Scope & Behavior:\n   - Core user goals & success criteria\n   - Explicit out-of-scope declarations\n   - User roles \u002F personas differentiation\n\n   Domain & Data Model:\n   - Entities, attributes, relationships\n   - Identity & uniqueness rules\n   - Lifecycle\u002Fstate transitions\n   - Data volume \u002F scale assumptions\n\n   Interaction & UX Flow:\n   - Critical user journeys \u002F sequences\n   - Error\u002Fempty\u002Floading states\n   - Accessibility or localization notes\n\n   Non-Functional Quality Attributes:\n   - Performance (latency, throughput targets)\n   - Scalability (horizontal\u002Fvertical, limits)\n   - Reliability & availability (uptime, recovery expectations)\n   - Observability (logging, metrics, tracing signals)\n   - Security & privacy (authN\u002FZ, data protection, threat assumptions)\n   - Compliance \u002F regulatory constraints (if any)\n\n   Integration & External Dependencies:\n   - External services\u002FAPIs and failure modes\n   - Data import\u002Fexport formats\n   - Protocol\u002Fversioning assumptions\n\n   Edge Cases & Failure Handling:\n   - Negative scenarios\n   - Rate limiting \u002F throttling\n   - Conflict resolution (e.g., concurrent edits)\n\n   Constraints & Tradeoffs:\n   - Technical constraints (language, storage, hosting)\n   - Explicit tradeoffs or rejected alternatives\n\n   Terminology & Consistency:\n   - Canonical glossary terms\n   - Avoided synonyms \u002F deprecated terms\n\n   Completion Signals:\n   - Acceptance criteria testability\n   - Measurable Definition of Done style indicators\n\n   Misc \u002F Placeholders:\n   - TODO markers \u002F unresolved decisions\n   - Ambiguous adjectives (\"robust\", \"intuitive\") lacking quantification\n\n   For each category with Partial or Missing status, add a candidate question opportunity unless:\n   - Clarification would not materially change implementation or validation strategy\n   - Information is better deferred to planning phase (note internally)\n\n3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:\n    - Maximum of 5 total questions across the whole session.\n    - Each question must be answerable with EITHER:\n       - A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR\n       - A one-word \u002F short‑phrase answer (explicitly constrain: \"Answer in \u003C=5 words\").\n    - Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.\n    - Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.\n    - Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness).\n    - Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests.\n    - If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic.\n\n4. Sequential questioning loop (interactive):\n    - Present EXACTLY ONE question at a time.\n    - For multiple‑choice questions:\n       - **Analyze all options** and determine the **most suitable option** based on:\n          - Best practices for the project type\n          - Common patterns in similar implementations\n          - Risk reduction (security, performance, maintainability)\n          - Alignment with any explicit project goals or constraints visible in the spec\n       - Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).\n       - Format as: `**Recommended:** Option [X] - \u003Creasoning>`\n       - Then render all options as a Markdown table:\n\n       | Option | Description |\n       |--------|-------------|\n       | A | \u003COption A description> |\n       | B | \u003COption B description> |\n       | C | \u003COption C description> (add D\u002FE as needed up to 5) |\n       | Short | Provide a different short answer (\u003C=5 words) (Include only if free-form alternative is appropriate) |\n\n       - After the table, add: `You can reply with the option letter (e.g., \"A\"), accept the recommendation by saying \"yes\" or \"recommended\", or provide your own short answer.`\n    - For short‑answer style (no meaningful discrete options):\n       - Provide your **suggested answer** based on best practices and context.\n       - Format as: `**Suggested:** \u003Cyour proposed answer> - \u003Cbrief reasoning>`\n       - Then output: `Format: Short answer (\u003C=5 words). You can accept the suggestion by saying \"yes\" or \"suggested\", or provide your own answer.`\n    - After the user answers:\n       - If the user replies \"yes\", \"recommended\", or \"suggested\", use your previously stated recommendation\u002Fsuggestion as the answer.\n       - Otherwise, validate the answer maps to one option or fits the \u003C=5 word constraint.\n       - If ambiguous, ask for a quick disambiguation (still the same question; do not advance).\n       - Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.\n    - Stop asking further questions when:\n       - All critical ambiguities resolved early (remaining queued items become unnecessary), OR\n       - User signals completion (\"done\", \"good\", \"no more\"), OR\n       - You reach 5 asked questions.\n    - Never reveal future queued questions in advance.\n    - If no valid questions exist at start, immediately report no critical ambiguities.\n\n5. Integration after EACH accepted answer (incremental update):\n    - Maintain an in-memory representation of the spec (loaded once at start) plus the raw file contents.\n    - For the first integrated answer this session: ensure a `## Clarifications` section exists (create it just after the highest-level contextual\u002Foverview section per the spec template if missing), and under it create a `### Session YYYY-MM-DD` subheading for today if not present.\n    - Append a bullet immediately after acceptance: `- Q: \u003Cquestion> → A: \u003Cfinal answer>`.\n    - Then immediately apply the clarification to the most appropriate section(s):\n       - Functional ambiguity → Update or add a bullet in Functional Requirements.\n       - User interaction \u002F actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.\n       - Data shape \u002F entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.\n       - Non-functional constraint → Add\u002Fmodify measurable criteria in Success Criteria > Measurable Outcomes (convert vague adjective to metric or explicit target).\n       - Edge case \u002F negative flow → Add a new bullet under Edge Cases \u002F Error Handling (or create such subsection if template provides placeholder for it).\n       - Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as \"X\")` once.\n    - If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.\n    - Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).\n    - Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.\n    - Keep each inserted clarification minimal and testable (avoid narrative drift).\n\n6. Validation (performed after EACH write plus final pass):\n   - Clarifications session contains exactly one bullet per accepted answer (no duplicates).\n   - Total asked (accepted) questions ≤ 5.\n   - Updated sections contain no lingering vague placeholders the new answer was meant to resolve.\n   - No contradictory earlier statement remains (scan for now-invalid alternative choices removed).\n   - Markdown structure valid; only allowed new headings: `## Clarifications`, `### Session YYYY-MM-DD`.\n   - Terminology consistency: same canonical term used across all updated sections.\n\n7. Write the updated spec back to `FEATURE_SPEC`.\n\n8. Report completion (after questioning loop ends or early termination):\n   - Number of questions asked & answered.\n   - Path to updated spec.\n   - Sections touched (list names).\n   - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial\u002FMissing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial\u002FMissing but low impact).\n   - If any Outstanding or Deferred remain, recommend whether to proceed to `\u002Fspeckit-plan` or run `\u002Fspeckit-clarify` again later post-plan.\n   - Suggested next command.\n\nBehavior rules:\n\n- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: \"No critical ambiguities detected worth formal clarification.\" and suggest proceeding.\n- If spec file missing, instruct user to run `\u002Fspeckit-specify` first (do not create a new spec here).\n- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).\n- Avoid speculative tech stack questions unless the absence blocks functional clarity.\n- Respect user early termination signals (\"stop\", \"done\", \"proceed\").\n- If no questions asked due to full coverage, output a compact coverage summary (all categories Clear) then suggest advancing.\n- If quota reached with unresolved high-impact categories remaining, explicitly flag them under Deferred with rationale.\n\nContext for prioritization: $ARGUMENTS\n\n## Post-Execution Checks\n\n**Check for extension hooks (after clarification)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.after_clarify` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.after_clarify` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs on phase completion.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - **Hook execution precedence** (D1): when `settings.auto_execute_hooks: true` in `.specify\u002Fextensions.yml`, a **mandatory** hook (`optional: false`) **auto-runs** with no confirmation; an **optional** hook (`optional: true`) is **always surfaced** (\"To execute: `\u002F{command}`\") and is **never force-run** by `auto_execute_hooks`; a hook with a non-empty `condition` is **never** evaluated by this skill — evaluation is left to the executor and the notice reports the resolved decision. When `auto_execute_hooks: false`, even mandatory hooks are surfaced for confirmation.\n  - **Effective-hooks notice** (D2): after the merge + dedup by `(extension, command)`, emit **one** consolidated notice for the phase so the operator never hand-reconciles files — the promoted feedback hook (`optional: false`) appears as `auto-run`, never as a surfaced optional:\n    ```\n    ## Effective hooks for clarify\n    - {extension}:{command} — auto-run        (mandatory; auto_execute_hooks=true)\n    - {extension}:{command} — surfaced        (optional)\n    - {extension}:{command} — skipped         (enabled: false)\n    - {extension}:{command} — condition-deferred\n    ```\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    ```\n",{"name":5,"metadata":23,"description":7,"compatibility":26},{"author":24,"source":25},"github-spec-kit","templates\u002Fcommands\u002Fclarify.md","Requires spec-kit project structure with .specify\u002F directory","main","f943406829a9218b2882e09eb88d4ddb539c5e72",".claude\u002Fskills\u002Fspeckit-clarify",0,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI","https:\u002F\u002Fgithub.com\u002FEHotwagner","2026-06-16 16:16:52",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-clarify",{"tool":40,"command":41},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-clarify",{"tool":43,"command":44},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-clarify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fspeckit-clarify\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M72SGYR4T02T1HTS175E0V86","fs-skia-ui-widgets","Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-ui-widgets\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M72SGVZJR1B117QK7TCC6E0J","fs-skia-testing","Assert generated-product expectations and evidence in a governed FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-testing\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M72SGTC5HZYEVVVZT4X51AZ3","fs-skia-skiaviewer","Wire a generated FS.Skia.UI product to the desktop viewer host.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-skiaviewer\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M72SGS47RPYPC9JTC39CC6EF","fs-skia-scene","Build pure scene descriptions in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-scene\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M72SGQF4G76C4NGSF69KZRRF","fs-skia-keyboard-input","Map keyboard input to product commands in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-keyboard-input\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M72SGNJP3PMSS2VRP98G7Z42","fs-skia-elmish","Drive a generated FS.Skia.UI product through the pure Elmish adapter.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-elmish\u002FSKILL.md",[],[]]