clarify

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.

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.

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.

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.

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.

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.