cf-clarify

Identify ambiguities in project design documents and propose clarifying questions.

2|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fimmtiu/code-factory --skill cf-clarify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-clarify
Source: https://github.com/fimmtiu/code-factory/tree/main/skills/cf-clarify
Command: npx skills add https://github.com/fimmtiu/code-factory --skill cf-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams surface ambiguities in a project design document so that implementers have a clear, actionable path to build from. It focuses on areas where details are underspecified, reducing rework and misinterpretation.

Core Features & Use Cases

  • Ambiguity scanning: automatically identifies unclear goals, functionality, scope, and success criteria in a design document.
  • Clarification guidance: proposes specific questions or clarifications to resolve each ambiguity.
  • Collaboration aid: supports planning reviews by highlighting gaps that team members should address before implementation.

Quick Start

Review the provided project specification and request a clarifying report that lists all ambiguities and suggested questions.

Frequently Asked Questions about cf-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify ambiguities in a project design document before implementation?

Spec-analysis tools identify ambiguities in a project design document by scanning Goals, Core Functionality, Scope/Boundaries, and Success Criteria. They output a concise report with actionable clarifying questions to resolve underspecified details.

What is the best way to clarify project specifications for software development?

Clarifying project specifications involves targeting areas where details are underspecified, reducing rework and misinterpretation. Surface specific questions or clarifications to resolve each ambiguity and guide implementers to a well-defined scope.

How do I resolve unclear requirements in a software planning document?

Resolving unclear requirements requires highlighting gaps that team members should address during planning reviews. Generate specific clarification guidance that proposes questions to resolve each ambiguity before implementation begins.

Can I use ambiguity scanning for any software project planning document?

Ambiguity scanning applies to plan-mode specifications across software initiatives. It targets project design documents containing Goals, Core Functionality, Scope/Boundaries, and Success Criteria to ensure a well-defined implementation scope.

Why does my software implementation fail due to underspecified project scope?

Implementation fails due to underspecified project scope because details remain ambiguous, leading to misinterpretation and rework. Scanning the spec for unclear boundaries and success criteria provides a clear, actionable path to build from.