sw-design

Software solution architecture involves researching your codebase and designing a structured solution before writing code. You need this process when starting a new feature to ensure your design aligns with existing project practices and avoids potential flaws.

You design software architecture by interactively researching existing code to inform decisions, proposing an architecture, and generating design artifacts like design.md and context.md. This ensures your new features integrate smoothly with the current project state.

Adversarial testing critiques your proposed solution architecture to identify flaws and risks early. Challenging your design adversarially ensures quality and trust, producing robust design artifacts before you commit to writing implementation code.

Yes, you can generate key design documents including design.md, context.md, and optionally decisions.md and data-model.md. These artifacts capture your software architecture and align it with your project configuration and existing state.

Yes, the solution design process works without external dependencies, relying instead on integrating directly with your project configurations and existing codebase state to guide the interactive architecture design and adversarial challenge workflow.