mcpField
C
clarify

clarify

github.com/yansfilDevelopment044 installsUpdated 19w ago
Repository

About clarify

clarify is a planning skill for requests with unresolved ambiguity. It helps teams inspect the repository, settle key decisions through focused questions, and produce a handoff a PRD writer can use.

Key features

  1. 01Restates the goal
  2. 02Explores repository context
  3. 03Prioritizes implementation decisions
  4. 04Asks one question at a time
  5. 05Tracks decisions and assumptions
  6. 06Defines a PRD-ready handoff

Use cases

  1. 01Clarifying scope before implementation
  2. 02Finding answers in project files
  3. 03Choosing between implementation options
  4. 04Preparing requirements for a PRD

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yansfil/vibe-engineering --skill clarify

After installing, type/clarifyin Claude Code to confirm it loaded.

Details

From the project README

clarify

Use this skill before planning or implementation when the request still has important ambiguity.

Do not write code, create a PRD, or change files while using this skill unless the user explicitly asks for notes to be saved.

Workflow

  1. Restate the current goal in 2-4 bullets.
  2. Explore the codebase freely as the conversation requires - read any docs, code, or config that could answer the question, and follow leads instead of asking the user what the repo can answer.
  3. Identify the 2-4 decisions that would most change the implementation.
  4. Ask one question at a time.
  5. For each question, include why it matters and a recommended default.
  6. Keep a compact running summary of decisions, assumptions, and deferred items.
  7. Stop when a PRD writer could proceed without guessing.

Question Rules

  • Ask the smallest useful question, not a survey.
  • Prefer concrete options with tradeoffs.
  • Do not ask the user for facts that the repository can answer.
  • If the user does not know, choose a tentative assumption and mark it clearly.
  • Push on vague words such as simple, fast, MVP, admin, secure, nice, and done.

Handoff Format

## Current Goal

- ...

## Decisions

- ...

## Assumptions

- ...

## Deferred

- ...

## PRD Input

- Problem:
- Users:
- Scope:
- Non-goals:
- Acceptance signals:

Comments

Markdown supported