research

Technical solution planning breaks down into phases: scope definition, multi-source information gathering with cited evidence, analysis against security and scalability criteria, and structured synthesis into actionable recommendations. This Skill automates that workflow to produce architecture decisions backed by research and risk assessment.

Structured technical research applies phase-driven scope definition to isolate what matters, gathers evidence from multiple sources with recency and credibility checks, then synthesizes findings into concise action plans. This approach ensures decisions rest on evidence rather than assumptions.

Applying YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself) principles during research planning constrains scope to functional requirements only. This Skill enforces those principles throughout analysis to keep solutions focused and maintainable.

Yes. Multi-source evaluation with explicit criteria for recency, source reliability, and security considerations lets you assess competing technologies systematically. The result is a decision-support report that compares options against your actual requirements.

Technical research produces report-ready structured output: phase definitions, cited evidence from multiple sources, analysis against your criteria, risk assessments, and actionable recommendations you can translate directly into architecture or implementation decisions.

The Skill handles research structure and synthesis. You provide the domain focus and criteria; the automation ensures comprehensive evidence gathering, consistent principle application, and organized output—reducing research overhead whether you're an expert or learning the domain.