pragmatic

Applies an action-first response style for routine tasks with clear requirements.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/alatyshau/duet --skill pragmatic-alatyshau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pragmatic
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/stances/pragmatic
Command: npx skills add https://github.com/alatyshau/duet --skill pragmatic-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When requirements are clear and the solution is obvious, lengthy explanations, alternative explorations, and trade-off tables slow down execution. This Skill switches the AI into a pragmatic stance that prioritizes immediate action over deliberation. ## Core Features & Use Cases - Action-First Responses: Executes the obvious solution immediately and reports results in one line, explaining only when asked. - Minimal Ceremony: Skips alternative exploration, trade-off tables, and unprompted long explanations for routine tasks like bug fixes, formatting, and small edits. - Automatic Escalation: Switches to a dialectic stance when the user pushes back, the solution fails, requirements contradict, or scope grows unexpectedly. - Use Case: You ask the AI to fix a known typo across several files. Instead of discussing approaches, it applies the fix and replies "Done. Updated 4 files." ## Quick Start Ask the AI to adopt the pragmatic stance and fix the known bug in the current file without discussing alternatives.

Frequently Asked Questions about pragmatic

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

FAQPage Schema
How do I make an AI assistant answer more concisely?

Adopt a pragmatic stance that instructs the AI to execute the obvious solution first and explain only when asked. Responses become one-line summaries like "Done. [summary]" with no trade-off tables or unprompted alternatives.

What response style works best for routine coding tasks?

For routine tasks like formatting, renaming, and small edits, an action-first style works best: pick the obvious solution, execute immediately, and keep responses short. Detailed explanations are reserved for cases where the user asks or the approach is non-obvious.

When should the pragmatic stance not be used?

Avoid it when requirements are ambiguous, contradictory, or the scope is growing unexpectedly. It is also unsuitable when the user pushes back or asks why, since those situations call for dialectic exploration of trade-offs and alternatives.

How does the AI know when to switch from pragmatic to dialectic mode?

The stance defines explicit switch triggers: the user pushes back or asks why, the chosen solution does not work, requirements seem contradictory, or the scope grows unexpectedly. Any of these signals a move to deeper deliberation.