skills.rest
reid15halo-ops
reid15halo-opsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

question

Prompt structured questions across scope, behavior, edge cases, UX, data, and integration.

Updated Aug 27, 2026
Search Tags:#planning#development#scoping#requirements#qa#clarification
One-click install
npx skills add https://github.com/reid15halo-ops/Local-Buisness-automizer --skill question-reid15halo-ops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: question
Source: https://github.com/reid15halo-ops/Local-Buisness-automizer/tree/main/.skills/question
Command: npx skills add https://github.com/reid15halo-ops/Local-Buisness-automizer --skill question-reid15halo-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all requirements and ambiguities are clarified before any implementation begins, preventing guesswork and rework.

Core Features & Use Cases

  • Requirements Clarification: Enforces a structured protocol for asking questions about scope, behavior, UX, data, and integration.
  • Codebase Research: Prompts the AI to research existing code and context before formulating questions.
  • Use Case: Before starting to implement a new feature, use this skill to ask targeted questions about its scope, edge cases, user interface, data storage, and integration points, ensuring a clear understanding of the task.

Quick Start

Use the question skill to clarify the requirements for adding a new dunning feature to the invoicing system.

Frequently Asked Questions about question

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

FAQPage Schema
How do I clarify software requirements before coding to prevent rework?▼

To clarify requirements before coding, enforce a structured clarification protocol that prompts detailed questions across scope, behavior, edge cases, UX, data persistence, and integration, preventing guesswork and rework.

What is the best way to scope feature development and identify edge cases?▼

Scoping feature development and identifying edge cases is best achieved by mandating pre-question research within the codebase and structuring inquiries for clarity. This addresses ambiguity in feature development tasks before implementation.

How do I structure questions for scoping a bug fix or refactoring task?▼

To structure questions for scoping a bug fix or refactoring task, use a requirements clarification protocol that covers scope, behavior, user interface, data storage, and integration points. This ensures a clear understanding of the task.

Can I research existing code context before generating requirements questions?▼

Yes, you can research existing code context before generating requirements questions. The protocol mandates pre-question research within the codebase to ensure inquiries are targeted and grounded in the actual application architecture.

Does requirements clarification work for complex integration and data persistence scoping?▼

Requirements clarification works for complex integration and data persistence scoping by prompting specific inquiries about data storage and integration points. This ensures all architectural ambiguities are resolved before implementation begins.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
team-attentionteam-attention
7

clarify:vague

Converts vague requests into actionable specifications using structured, hypothesis-driven questioning and summaries.

Official
Intermediate
PacificStudioPacificStudio
264

write-test

Design focused tests verifying behavior contracts and key edge cases.

Official
Intermediate
yangsi7yangsi7

Specification Clarification

Identify and resolve specification ambiguities through structured questioning.

Community
Basic