speckit-clarify is agent-read markdown (skill) from rshade/finfocus: Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## User Input
```text
$ARGUMENTS
```
You **MUST** consider the user input before proceeding (if not empty).
## Pre-Execution Checks
**Check for extension hooks (before clarification)**:
- Check if `.specify/extensions.yml` exists in the project root.
- If it exists, read it and look for entries under the `hooks.before_clarify` key
- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
- If the hook has no `condition` field, or it is null/empty, treat the hook as executable
- If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_amkmd57mux6i5chu
GET https://markdownregistry.com/api/v1/resolve?ref=rshade/finfocus/speckit-clarify
GET https://markdownregistry.com/api/v1/blob/27969ae8948029ff8f3ebb4732bbc786817689388c5d8dc5b65897320cb8a96f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
rshade/finfocus · .agents/skills/pick-issue/SKILL.md · Pick the next GitHub issue(s) to work on from the finfocus roadmap backlog and optionally promote them to…
rshade/finfocus · .claude/skills/finfocus-cost/finfocus-cost/SKILL.md · Guide for using FinFocus CLI to analyze cloud infrastructure costs. Use when running projected or actual cost commands…
rshade/finfocus · .claude/skills/finfocus-dev/finfocus-dev/SKILL.md · FinFocus Core development workflow guide for contributors. Use when implementing features, fixing bugs, writing tests…
rshade/finfocus · .claude/skills/finfocus-plugin/finfocus-plugin/SKILL.md · Guide for building FinFocus cost plugins using the pluginsdk and gRPC protocol. Use when creating a new plugin…
rshade/finfocus · .kimi-code/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…
rshade/finfocus · .kimi-code/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs.
rshade/finfocus · .kimi-code/skills/speckit-converge/SKILL.md · Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new…
rshade/finfocus · .kimi-code/skills/speckit-implement/SKILL.md · Execute the implementation plan by processing and executing all tasks defined in tasks.md
oryx-labs/oryxos · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
pisberg/vibetags · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
