discover

Probe ambiguous requirements across eight completeness dimensions using AskUserQuestion.

54|3|Updated Feb 4, 2026

Search Tags:#planning #requirements #discovery #clarification #assumptions #interrogation

Ready to run

npx skills add https://github.com/arcasilesgroup/ai-engineering --skill discover-arcasilesgroup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.agents/skills/discover
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill discover-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all necessary requirements, assumptions, and potential risks are identified and clarified before starting any non-trivial feature development, preventing scope creep and misunderstandings.

Core Features & Use Cases

Structured Interrogation: Systematically probes for missing information across 8 key dimensions (scope, success criteria, constraints, etc.).
Context Harvesting: Analyzes existing documentation and code to categorize information as Known, Assumed, or Unknown.
Use Case: Before starting a new feature, use this skill to ask targeted questions that uncover hidden assumptions about user behavior or technical limitations, ensuring the team plans for all eventualities.

Quick Start

Use the discover skill to interrogate requirements for the new user authentication module.

Frequently Asked Questions about discover

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

FAQPage Schema

What is requirements discovery and why is it needed before feature planning?▼

Requirements discovery identifies hidden assumptions and gaps by probing ambiguous requests. It categorizes existing context into known, assumed, or unknown information to prevent scope creep and misunderstandings before development begins.

How do I clarify ambiguous user requests for a new software feature?▼

You clarify ambiguous user requests by systematically probing for missing information using targeted questions. This structured interrogation surfaces hidden assumptions about user behavior and technical limitations across multiple completeness dimensions.

What dimensions should I check for completeness when gathering project requirements?▼

You should check for completeness across eight dimensions: functional, non-functional, security, integration, migration, testing, documentation, and governance. This ensures all potential risks and constraints are identified before planning.

Can I use structured interrogation to identify assumptions in existing documentation?▼

Yes, you can use structured interrogation to analyze existing documentation and code. This context harvesting process categorizes the information into known, assumed, or unknown buckets to expose gaps across the eight completeness dimensions.

What is the best way to prevent scope creep during non-trivial feature development?▼

The best way to prevent scope creep is to perform systematic requirements discovery before development. Relentless interrogation of constraints and assumptions ensures all necessary requirements and risks are identified early.