util-ask

Prompt targeted architectural questions from plans and architecture documents.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill util-ask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: util-ask
Source: https://github.com/JSai23/claude-tooling/tree/main/compiled/util/agentskills/util-ask
Command: npx skills add https://github.com/JSai23/claude-tooling --skill util-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams clarify design decisions and architectural trade-offs by prompting focused questions early in the lifecycle, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured questioning framework to surface assumptions, constraints, and dependencies.
  • Context-aware prompts that reference plans and architecture documents to stay aligned.
  • Decision capture and rationale tracing to support future reviews and onboarding.

Quick Start

Ask a clarifying question about the current design to align on architecture.

Frequently Asked Questions about util-ask

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

FAQPage Schema
How do I clarify architecture decisions and surface hidden design assumptions early?

You can clarify architecture decisions by applying a structured questioning framework that prompts targeted questions, surfacing hidden assumptions, constraints, and dependencies to reduce ambiguity and rework.

What is the best way to align on system design before starting feature scoping?

Aligning on system design is best achieved by using context-aware prompts that reference existing plans and architecture docs, ensuring feature scoping stays aligned with established project conventions.

How do I prompt targeted architectural questions for a system decomposition task?

You prompt targeted architectural questions for system decomposition by referencing your architecture docs and plans to guide the inquiry, adhering to project conventions while avoiding code-level implementation details.

Can I use existing plans and architecture docs to trace design rationale during reviews?

Yes, existing plans and architecture docs support decision capture and rationale tracing, providing a clear record of architectural trade-offs for future reviews and team onboarding.

Does this approach generate code-level implementation details for the architecture?

No, this approach explicitly avoids code-level implementation details, focusing entirely on clarifying architectural trade-offs, system decomposition, and design decisions at a higher abstraction level.