discovery-phase

Automate library and integration evaluations by running a depth-aware discovery workflow that compares options using Context7 MCP, web search, and official docs to validate findings. It generates a DISCOVERY.md summarizing sourced options and confidence assessments for plan-phase alignment.

A DISCOVERY.md file is a structured document summarizing evaluated options, findings, sources, and confidence assessments. You need it when comparing libraries or integrations to ensure traceability of architectural conclusions and inform PLAN.md creation.

Control discovery depth by selecting a specific level parameter: verify, standard, or deep dive. These depth-controlled levels match your time and risk constraints, ensuring the evaluation output aligns with the required architectural decision-making rigor.

The discovery workflow requires Context7 MCP and web search to source and validate findings. It uses these tools alongside official documentation to compare options and ensure the output structure includes verifiable sources and a clear confidence assessment.

The best way to structure source-backed option comparisons is to generate a DISCOVERY.md with a clear output structure. It summarizes options, findings, and sources, providing a defensible comparison that ensures traceability of conclusions for architectural alignment.

Your architectural decision process lacks traceability when it does not use a structured, source-backed discovery workflow. Automating this process produces a DISCOVERY.md that validates findings with Context7 and web sources, ensuring defensible comparisons and plan-phase alignment.