intent-discovery

Guide feature design through requirement clarification and approach evaluation.

78|20|Updated Mar 9, 2026

Search Tags:#design #planning #architecture #specification #requirements #validation

Ready to run

npx skills add https://github.com/NoobyGains/godmode --skill intent-discovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-discovery
Source: https://github.com/NoobyGains/godmode/tree/main/skills/intent-discovery
Command: npx skills add https://github.com/NoobyGains/godmode --skill intent-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents the AI from jumping into implementation without a clear, user-approved design, mitigating the risk of building the wrong thing and saving significant rework.

Core Features & Use Cases

Structured Design Process: Guides raw ideas through a dialogue into fully specified, validated designs.
Requirement Clarification: Asks targeted questions to understand purpose, constraints, and success criteria.
Approach Evaluation: Presents 2-3 distinct implementation approaches with trade-offs for user selection.
Use Case: When asked to "build a user authentication system," this skill will first explore requirements, propose design options (e.g., JWT vs. session-based, OAuth integration), and get user approval on the architecture before any code is written.

Quick Start

Use the intent-discovery skill to start designing the new user profile feature.

Frequently Asked Questions about intent-discovery

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

FAQPage Schema

How do I prevent AI from jumping straight into coding before the architecture is finalized?▼

To prevent premature coding, use a specification-first approach that guides the AI through a structured design process, ensuring user intent and design trade-offs are validated before implementation begins.

What is the best way to define requirements and evaluate design trade-offs for a new feature?▼

Defining requirements involves targeted questions to clarify purpose and constraints, while evaluating design trade-offs is best handled by presenting 2-3 distinct implementation approaches for user selection and approval.

How do I validate system design intent before starting software implementation?▼

You validate system design intent by exploring requirements and proposed architectures through a structured dialogue, getting explicit user approval on the selected approach before any code is written.

Does this structured design process work for complex system modifications like building a user authentication system?▼

Yes, this structured design process works for complex modifications like a user authentication system by exploring requirements, proposing design options such as JWT versus session-based, and validating the architecture first.

When should I use a specification-first design approach instead of direct implementation?▼

You should use a specification-first design approach whenever building new features or components, as it mitigates the risk of building the wrong thing and saves significant rework by ensuring alignment with project goals.