design

To explore architectural design options, you provide a Basecamp todo URL, local markdown file, or interactive feature description. The tool analyzes your codebase context to generate multiple competing design proposals for evaluation.

Comparing architectural proposals against software design principles is done by generating multiple distinct blueprints and evaluating them using principle-based critique. This process highlights the pros, cons, and best practices for each design path.

Yes, you can use local markdown files to provide context for codebase analysis during feature architecture planning. The system leverages existing codebase patterns and documentation from these files to ground its architectural design proposals.

Yes, architectural exploration works directly with Basecamp todo URLs as a valid input format. The system extracts the feature requirements from the URL to generate and evaluate competing architectural design proposals.

Codebase analysis improves software design decision making by grounding new feature proposals in your existing code patterns and documentation. This ensures generated architectural blueprints align with the current codebase context before synthesizing a final recommendation.

You should avoid generating multiple competing design proposals when the feature scope is too narrow to warrant distinct architectural blueprints. The tool is designed for complex features requiring principle-based critique and codebase analysis to ensure robust design decisions.