solution-designer

Compare implementation approaches for Kotlin Telegram bot features across Clean Architecture layers.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Astrumon/Spovishun --skill solution-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-designer
Source: https://github.com/Astrumon/Spovishun/tree/main/.claude/skills/solution-designer
Command: npx skills add https://github.com/Astrumon/Spovishun --skill solution-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity when choosing how to implement a feature by comparing concrete implementation approaches against Spovishun's existing conventions and Clean Architecture layers, helping teams pick the simplest, most consistent solution.

Core Features & Use Cases

  • Side-by-side option generation: Produce 2–3 concrete implementation options for a feature, each with an approach summary, affected layers, key file-level changes, and any required migrations or new dependencies.
  • Consistency-first evaluation: Validate options against existing patterns in the Spovishun codebase (presentation → domain ← data) and prefer established patterns.
  • Decision handoff: Produce a compact Solution Decision document and call out next steps for task decomposition and implementation.
  • Use Case: When adding a new group-tagging command, use this Skill to compare an in-controller approach, a domain-service approach, and a data-layer optimized approach and choose the best fit.

Quick Start

Use the solution-designer skill to compare two implementation approaches for a given feature and produce 2–3 options, a comparison matrix, and a recommended Solution Decision.

Frequently Asked Questions about solution-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate implementation options for a new feature in a Kotlin Telegram bot?

Evaluating implementation options involves comparing 2–3 concrete approaches against existing Clean Architecture layers (presentation, domain, data, DI), identifying tradeoffs, affected files, migrations, and dependencies, and producing a comparison matrix with a recommended solution decision.

What is solution design for feature-level Kotlin development?

Solution design for feature-level Kotlin development is the process of comparing concrete implementation approaches for a specific feature, validating them against existing codebase conventions, and avoiding system-level architectural changes to ensure consistency and simplicity.

How do I compare architectural tradeoffs when adding a new command to a Clean Architecture codebase?

Comparing architectural tradeoffs involves generating side-by-side implementation options—such as an in-controller approach versus a domain-service approach—evaluating their consistency with established patterns, and outputting a Solution Decision document for downstream task decomposition.

Can I use this approach for system-level architectural redesigns?

No, this approach is strictly limited to feature-level design questions within existing presentation, domain, data, and DI layers, intentionally avoiding system-level architectural changes to maintain established codebase conventions and simplicity.

What does a solution decision document include for Telegram bot features?

A solution decision document includes 2–3 concrete implementation options, a comparison matrix, affected file-level changes, required migrations, new dependencies, and a final recommended solution decision suitable for downstream task decomposition.