explore

To map project requirements before coding, you need a structured thinking environment that scans existing documentation and navigation files to understand project conventions. This prevents premature implementation and architectural drift by analyzing requirements collaboratively.

The best way to investigate complex architectural problems is by using a thinking partner that aligns business goals with technical specifications. It provides context-aware analysis by mapping project-level orientation files to ensure solutions fit existing ADRs.

Context mapping works by automatically scanning project documentation and navigation files to understand the project's unique structure. This grounded analysis ensures that design exploration and visual brainstorming align with actual codebase constraints.

Yes, you can use ASCII diagrams for comparative analysis of different technical approaches. The design exploration process facilitates visual brainstorming, allowing you to compare architectural solutions directly within your project context.

Yes, you need access to project-level orientation files and documentation to analyze architectural drift effectively. The analysis requires these inputs to provide grounded, context-aware investigation and ensure alignment between business goals and technical specifications.

You should not use a collaborative thinking partner when you have clear, finalized specifications ready for immediate implementation. It is designed for the investigation and mapping phase to prevent premature implementation, not for generating final production code.