design-log

A research-driven design process integrates external search and structured documentation into software planning, ensuring features are thoroughly researched and evaluated before implementation begins. This approach prevents overlooked edge cases in complex refactors.

You can document software design decisions by running a structured planning protocol that automatically generates a comprehensive design log file, capturing research findings and design rationale for large features and refactors.

The best way to plan a large software refactor is using a five-phase stop-and-think protocol that incorporates web research to inform design decisions, ensuring thorough consideration of impacts before any code execution begins.

Yes, this structured design documentation workflow requires multiple research MCPs including Tavily, Exa, and Firecrawl to gather external research, followed by collaboration with a tech-researcher skill to inform the planning phases.

This planning protocol is designed for large features, complex fixes, and major refactors where careful consideration is critical. Small bug fixes do not require the extensive five-phase research and documentation overhead.

Software planning often lacks design consideration when it skips a structured stop-and-think phase, missing research-driven evaluation that integrates external sources and automated documentation before implementation.