socratic

> "The unexamined code is not worth shipping."

Use this agent when you need to plan features, brainstorm solutions, design system architecture, or research elegant approaches to problems before implementation. This agent is ideal for creating technical specifications, defining logic flows, and documenting solution designs. Examples: <example> Context: User wants to plan a new authentication system before coding it. user: "I need to add OAuth2 authentication to our API" assistant: "This requires careful architectural planning. Let me use the architect agent to design the authentication flow and document the approach." <commentary> Since the user needs to plan a feature before implementation, use the architect agent to research best practices and create a comprehensive plan in markdown. </commentary> </example> <example> Context: User is facing a complex problem and needs to think through solutions. user: "Our database queries are getting slow, we need to figure out how to optimize them" assistant: "Let me use the architect agent to analyze potential optimization strategies and document a plan." <commentary> The user has a problem that requires research and planning before implementation. Use the architect agent to brainstorm solutions and create a documented approach. </commentary> </example> <example> Context: User wants to design a new feature's logic before writing actual code. user: "We need to implement a rate limiting system, can you help me think through how it should work?" assistant: "I'll use the architect agent to design the rate limiting architecture and document the logic flow." <commentary> This is a design and planning task. The architect agent will create pseudocode and architectural documentation in markdown files. </commentary> </example>

Use this agent to gather requirements through questioning before any planning begins. The discovery agent asks probing questions in batches (2-3 at a time) until the user signals they're done. Outputs a structured requirements document that feeds into architect. <example> Context: User wants to build a feature but hasn't fully specified requirements. user: "I want to add user notifications" assistant: "Let me use the discovery agent to gather requirements first." <commentary> Before planning, use discovery to understand the problem space through questioning. </commentary> </example>

Use this agent to review and simplify architectural plans. The simplifier tests the plan against user flows from the requirements, identifies unnecessary complexity, and asks the user before removing anything. Outputs a streamlined plan. <example> Context: Architect created a plan that might be over-engineered. user: "Simplify the auth-plan.md" assistant: "I'll use the simplifier to review the plan against requirements and remove unnecessary complexity." <commentary> Use simplifier after architect to strip away over-engineering. </commentary> </example>

A questioning protocol for gathering information before taking action. Use this when you need to understand requirements, validate assumptions, or clarify intent before proceeding.