clarify

Resolve ambiguities by updating documents with tracked changes.

1|Updated Jan 12, 2026

Search Tags:#workflow #documentation #ambiguity #review #spec #audit-trail #clarify

Ready to run

npx skills add https://github.com/srnnkls/tropos --skill clarify-srnnkls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/srnnkls/tropos/tree/main/skills/clarify
Command: npx skills add https://github.com/srnnkls/tropos --skill clarify-srnnkls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve ambiguities interactively by updating documents directly with tracked changes, preserving an audit trail across specs, reviews, and related work.

Core Features & Use Cases

Update source documents in context (specs, code reviews) with tracked changes.
Detect and prioritize ambiguity gaps, open markers, and questions for clarification.
Maintain an auditable session log that records questions, answers, and document updates.

Quick Start

Initiate a clarification session by loading the relevant context (spec, code-review, or standalone) and begin presenting candidates to resolve.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I resolve ambiguity in a project spec without losing the original context?▼

To resolve ambiguity in a project spec without losing context, you can update source documents directly using tracked changes. This preserves the original text while recording questions, answers, and updates in an auditable session log.

What is the best way to track unresolved questions and open markers during a spec review?▼

The best way to track open markers during a spec review is to run a structured clarification session. This process detects ambiguity gaps, presents candidates for resolution, and maintains an audit trail of all document updates.

Can I use tracked changes to clarify scope and data model issues across standalone tasks?▼

Yes, you can use tracked changes to clarify scope and data model issues across standalone tasks. The system applies contextual detection to update source documents directly, ensuring clarity across various collaboration workflows.

How do I audit document updates made during code review clarifications?▼

You audit document updates made during code review clarifications by accessing the session log. This log records presented questions, provided answers, and tracked changes applied directly to the source documents.

Does this clarification workflow require any external dependencies or specific component integrations?▼

No, this clarification workflow does not require external dependencies or specific component integrations. It operates as a standalone advanced process to detect ambiguities, present clarification candidates, and update documents with an audit trail.