design-pragmatist_skill

This skill helps evaluate design proposals for real-world feasibility, team capability, timelines, maintenance cost, and proven patterns to ensure practical
  • Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill design-pragmatist

  • SKILL.md2.0 KB

Overview

This skill provides practical design analysis focused on real-world feasibility, team fit, timeline realism, maintenance cost, and use of proven solution patterns. It helps decision-makers and engineers surface implementation risks and actionable mitigations. The output grades proposals with clear strength ratings to guide go/no-go and next-step planning.

How this skill works

The skill inspects a design proposal against a checklist: feasibility with available tools, realism of infrastructure assumptions, team capabilities and staffing, timeline and integration complexity, maintenance burden, and adherence to proven patterns. It identifies risky assumptions, dependency concerns, and opportunities to reuse existing solutions, then assigns a strength rating: Strong, Moderate, Weak, or Neutral. Recommendations include concrete mitigation steps, prototyping focuses, and documentation or monitoring needs.

When to use it

  • Evaluating architecture decisions before committing significant resources
  • Reviewing vendor solutions or new technologies for production readiness
  • Assessing proposals that require cross-team coordination or hiring
  • Prioritizing work that impacts long-term maintenance and operational cost
  • Deciding between building custom features versus buying or reusing

Best practices

  • Validate risky areas with a time-boxed prototype or proof-of-concept
  • Map required skills and confirm team capacity before scheduling work
  • Prefer well-established patterns unless a clear, documented benefit exists
  • Factor operational needs (monitoring, debugging, updates) into initial design
  • Document assumptions, dependencies, and rollback criteria early

Example use cases

  • Reviewing a microservices split to verify deployment and monitoring readiness
  • Assessing adoption of a new database or queue technology for production use
  • Deciding whether to rewrite a legacy module or extend the current system
  • Estimating realistic timelines when introducing unfamiliar frameworks
  • Comparing build-vs-buy options for a third-party authentication provider

FAQ

Strong means low risk and proven approach; Moderate indicates manageable trade-offs; Weak flags major feasibility risks; Neutral means missing information prevents assessment.

How detailed should the prototype be?

Keep prototypes focused on the riskiest integrations or performance assumptions and limit scope to deliver quick, informative results within a few days to a few weeks.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
design-pragmatist skill by shotaiuchi/dotclaude | VeilStrat