clarify

Scan design documents to identify and log unresolved implementation decisions.

Updated Apr 12, 2026

Search Tags:#workflow #planning #documentation #implementation #clarification #decision-making

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill clarify-olivermorgan2

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the "gray areas" in project requirements that are too small for an ADR but too significant to ignore, preventing technical debt and scope creep during execution.

Core Features & Use Cases

Gray Area Detection: Automatically scans PRDs, MVP docs, and planning files to identify unresolved implementation questions.
Decision Logging: Appends settled decisions to a centralized log, ensuring team alignment without the overhead of formal architectural documentation.
Use Case: Use this when you have a clear MVP but need to decide on minor implementation details like specific UI depth limits or SSO provider choices before starting development.

Quick Start

Run the clarify skill to scan your design documents and surface unresolved implementation questions for resolution.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I resolve minor implementation ambiguities in my MVP documentation before coding?▼

To resolve implementation ambiguities before coding, scan your MVP documentation and codebase patterns to identify gray areas, then append the settled decisions to a centralized log. This prevents technical debt and scope creep during execution.

What is the best way to surface unresolved planning questions from a PRD without writing formal ADRs?▼

Surfacing unresolved planning questions without formal ADRs involves scanning your PRD and planning files to detect implementation gray areas. You then log these decisions centrally to ensure team alignment without the overhead of architectural documentation.

How do I track implementation decisions for UI depth limits or SSO providers during project scoping?▼

Track implementation decisions for details like UI depth limits or SSO providers by maintaining an append-only decision log. Scanning your design and MVP docs surfaces these specific gray areas for disciplined resolution before development begins.

Do I need specific design files to start clarifying project requirements and scope?▼

You need access to design/prd-normalized.md and design/mvp.md to start clarifying requirements. An optional design/planning.md file can also be included to maintain an append-only decision log for your project.

When should I not use automated gray area detection for project planning?▼

You should not use automated gray area detection for architectural decisions requiring formal documentation. It is designed specifically for unresolved implementation details that are too small for an ADR but too significant to ignore during MVP scoping.

Can I apply implementation clarification workflows to non-software projects?▼

You can apply implementation clarification workflows to non-software projects requiring disciplined decision-making. The process scans available project documentation to resolve gray areas between MVP scoping and execution.