Create a discovery document to gather and clarify requirements
Scanned 9/5/2026
Install to Claude Code
npx -y skills add dvcrn/openclaw-skills-marketplace --skill discovery --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discovery?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dvcrn-discovery)More formats (shields.io, HTML) on the badges page.
---
name: discovery
description: Create a discovery document to gather and clarify requirements
metadata: {"openclaw":{"requires":{"bins":["git"]}}}
user-invocable: true
---
# Discovery
Create a discovery document for gathering and clarifying requirements before creating an implementation plan.
## What It Does
1. Gathers functional and non-functional requirements
2. Documents constraints and dependencies
3. Identifies open questions that need answers
4. Proposes a high-level approach
5. Documents risks and unknowns
## Usage
```
/discovery <topic>
```
**Arguments:**
- `topic` (required): The feature or topic to discover requirements for
## Output
Creates: `flow/discovery/discovery_<topic>_v<version>.md`
## Document Structure
```markdown
# Discovery: [Topic]
## Context
Why this discovery is needed
## Requirements Gathered
### Functional Requirements
- [FR-1]: Description
### Non-Functional Requirements
- [NFR-1]: Description
### Constraints
- [C-1]: Description
## Open Questions
| # | Question | Status | Answer |
|---|----------|--------|--------|
| 1 | Question | Open | - |
## Technical Considerations
Architecture, dependencies, patterns
## Proposed Approach
High-level recommendation
## Risks and Unknowns
Identified risks with mitigation strategies
## Next Steps
Follow-up actions
```
## Example
```
/discovery user authentication with OAuth
```
**Creates:** `flow/discovery/discovery_user_authentication_with_oauth_v1.md`
## Critical Rules
- **No Code**: Discovery is for gathering requirements only. No implementation.
- **Ask Questions**: Use interactive questions to clarify unclear requirements.
- **Mark Assumptions**: Always explicitly mark assumptions for validation.
## Next Command
After discovery, run `/create-plan @flow/discovery/discovery_<topic>_v1.md` to create an implementation plan.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!