skills.rest
alatyshau
alatyshauCOMMUNITY
Explore all skills by this author →
GitHub

dialectic

Guides exploratory reasoning for architecture decisions and ambiguous requirements before concluding.

Updated Nov 21, 2025
Search Tags:#architecture#decision making#requirements#reasoning#exploration#trade-off analysis#dialectic
One-click install
npx skills add https://github.com/alatyshau/duet --skill dialectic-alatyshau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dialectic
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/stances/dialectic
Command: npx skills add https://github.com/alatyshau/duet --skill dialectic-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing ambiguous requirements, architecture decisions, or multiple valid approaches, AI assistants often jump to a single solution prematurely. This Skill enforces a dialectic stance that explores trade-offs, questions assumptions, and keeps options open before committing. ## Core Features & Use Cases - Assumption Questioning: Prompts the AI to identify the real problem and audience before answering. - Trade-off Analysis: Encourages naming tensions explicitly and comparing alternatives in tables rather than converging early. - Explicit Uncertainty: Ends responses with open questions or explicit "holding open" statements instead of hiding doubt. - Use Case: When a user says "just make it work" on a system design task, the Skill drives the AI to surface unstated needs, present multiple approaches with trade-offs, and only switch to execution once requirements are clear. ## Quick Start Ask the AI to help you decide between two architecture approaches and request that it explore trade-offs before recommending one.

Frequently Asked Questions about dialectic

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

FAQPage Schema
How do I get an AI to explore options instead of jumping to a solution?▼

Use a dialectic stance that instructs the AI to question assumptions, list alternatives with trade-offs, and end with open questions. This prevents premature convergence on a single option when requirements are ambiguous.

What is the dialectic approach for architecture decisions?▼

The dialectic approach explores before concluding: identify the real problem and audience, compare alternatives in trade-off tables, and name tensions explicitly. It avoids presenting one option as obvious until the decision criteria are clear.

When should I switch from exploration to execution mode?▼

Switch to a pragmatic execution stance when the user explicitly wants speed, requirements become clear, or a decision has been made. The dialectic stance is for exploration, not for implementing settled decisions.

What are the limitations of exploratory reasoning in AI assistants?▼

Exploratory reasoning slows down responses and can frustrate users who want quick answers. It is unsuitable for well-defined tasks with clear requirements, where direct execution produces better results.

Related Skills

Explore More Software Engineering Skills→
DanialHaseebDanialHaseeb

shape

Plan UX and UI through structured discovery interviews and design briefs.

Community
Intermediate
cynkracynkra
1

openspec-explore

Investigate codebase architecture and draft OpenSpec artifacts without implementing code.

Official
Basic
anthropicsanthropics
23.4k

architecture

Create and evaluate Architecture Decision Records for system design choices.

Official
Intermediate
brolagbrolag
11

parallel-verification

Explore multiple reasoning paths in parallel to verify high-stakes solutions.

Community
Advanced