skills.rest
carl10086
carl10086COMMUNITY
Explore all skills by this author →
GitHub

explore-then-ask

Guides requirement clarification and architectural design through structured dialogue.

7|Updated Apr 10, 2026
Search Tags:#workflow#design#architecture#requirements#clarification#sop
One-click install
npx skills add https://github.com/carl10086/ys-powers --skill explore-then-ask
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explore-then-ask
Source: https://github.com/carl10086/ys-powers/tree/main/skills/explore-then-ask
Command: npx skills add https://github.com/carl10086/ys-powers --skill explore-then-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of unexamined assumptions and poorly defined requirements in software projects by enforcing a structured, dialogue-driven design process before any implementation begins.

Core Features & Use Cases

  • Structured Clarification: Guides the user through a step-by-step process to define purpose, constraints, and success criteria.
  • Design Validation: Ensures architectural decisions are presented in manageable sections for user approval, preventing wasted development effort.
  • Use Case: When starting a new feature, use this skill to explore existing project context and historical SOPs, then iteratively refine the design through conversational trade-off analysis.

Quick Start

Invoke the explore-then-ask skill to begin a structured design session for your current project idea.

Frequently Asked Questions about explore-then-ask

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

FAQPage Schema
How do I clarify vague software requirements before writing code?▼

Requirement clarification prevents wasted development effort by validating architectural decisions in manageable sections for user approval. It ensures unexamined assumptions and poorly defined constraints are resolved through conversational trade-off analysis.

What is the best way to validate architectural design within an existing project context?▼

Yes, you can integrate historical SOPs and domain-specific documentation during requirement clarification. The methodology operates within existing project contexts to refine architectural designs through conversational trade-off analysis.

How do I start a structured design session for a new software feature?▼

To start a structured design session, invoke a dialogue-first methodology to explore the current project idea. It guides you step-by-step through structured clarification to define purpose, constraints, and success criteria before implementation.

Why should I separate design exploration from code generation?▼

Limitations arise if you skip the structured clarification process, risking wasted effort on misaligned architecture. The methodology strictly requires validating design exploration and historical SOP integration before proceeding to code generation.

Related Skills

Explore More Software Engineering Skills→
wizactwizact

spec-context

Parse GitHub issues and project documentation to generate context.json files.

Community
Advanced
ScarletFishScarletFish

code-architect

Analyze codebase patterns to generate implementation blueprints for new features.

Community
Advanced
davpatel605-beepdavpatel605-beep

bioinformatics

Retrieve domain-specific bioinformatics references for computational biology workflows.

Community
Advanced
sustinbebustinsustinbebustin

spec-planner

Guides iterative clarification and drafting of implementation-ready specifications for software features and architectural decisions.

Community
Advanced