Software design plans with clear trade-offs.
Creates technical design documents that explain implementation options and architectural trade-offs.
When to use it
Use for solution, architecture, or technical design requests that do not ask for a PRD.
Give it a software design problem and the project; it asks clarifying questions, reviews the codebase, and writes a technical design in the project's docs/ directory.
What you provide
An after-completion hook triggers self-improving-agent in the background to learn from architecture patterns; whether installation is required is unstated.
An after-completion hook automatically triggers session-logger to log the architecture design; whether installation is required is unstated.
This skill
web search results
Searches for architecture best practices