skills.rest
mpazaryna
mpazarynaCOMMUNITY
Explore all skills by this author →
GitHub

dev-inquiry

Guide structured technical inquiry across investigation, spike, comparison, and decision modes.

1|Updated Sep 17, 2025
Search Tags:#architecture#investigation#validation#comparison#decision-making#technical-spike#feynman
One-click install
npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-inquiry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-inquiry
Source: https://github.com/mpazaryna/claude-toolkit/tree/main/generated-skills/dev-inquiry
Command: npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-inquiry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly technical decisions by ensuring you thoroughly investigate, validate, and compare options before committing to implementation.

Core Features & Use Cases

  • Investigation Mode: Feynman-style exploration to build mental models through experimentation.
  • Spike Validation: Time-boxed TDD approach to prove technical feasibility before building.
  • Use Case: When your team needs to choose between SwiftData and CoreData, this Skill guides you through understanding both technologies, validating your assumptions with real code, and making evidence-based decisions.

Quick Start

Use the dev-inquiry skill to explore SwiftUI macros and understand how they work.

Frequently Asked Questions about dev-inquiry

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

FAQPage Schema
How do I make better technical decisions when evaluating unfamiliar technologies?▼

Structured technical inquiry guides you through investigation, validation, and comparison before committing. Build mental models through experimentation, validate assumptions with time-boxed code spikes, and gather evidence to support decisions rather than relying on assumptions alone.

What's the best way to choose between competing architectural patterns or frameworks?▼

Compare options systematically by first understanding each through hands-on exploration, then proving feasibility with real code before formal comparison. Document findings and trade-offs to create evidence-driven recommendations your team can trust.

How do I avoid analysis paralysis when my team needs to pick a new technology?▼

Time-boxed investigation modes prevent endless deliberation. Use structured workflows for exploration and spike validation to reach testable outcomes quickly, turning uncertainty into documented evidence that justifies your choice.

Can I validate technical assumptions before building a full implementation?▼

Yes. Spike validation uses time-boxed TDD to prove feasibility with minimal code, catching blockers early without the cost of production implementation.

What role does hands-on experimentation play in technical decision-making?▼

Feynman-style exploration builds accurate mental models through direct experimentation rather than theory alone. Real code spikes reveal hidden constraints and performance characteristics that comparison alone cannot surface.

Related Skills

Explore More Software Engineering Skills→
jamestorrevillasjamestorrevillas
3

tech-research

Evaluate and compare technology options using a six-step decision framework.

Community
Advanced
cyberpunk042cyberpunk042

feature-review

Reconstruct feature contracts from artifacts and generate formal verification verdicts.

Community
Advanced
drt0927drt0927
5

plan-eng-review

Orchestrate engineering plan reviews covering architecture, data flow, and test coverage.

Community
Advanced
ZacharyLuzZacharyLuz
5

evaluation

Standardize technology evaluations with weighted criteria and scoring matrices.

Community
Advanced