Skip to content
Back to skills

Discovery

ASecurity

Create a discovery document to gather and clarify requirements

  • 33 stars
  • 0 votes
  • 4 copies
  • 47 views
  • Added September 5, 2026
securitygit

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add dvcrn/openclaw-skills-marketplace --skill discovery --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discovery?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Discovery
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dvcrn-discovery/badge)](https://www.skillsdirectory.com/skills/dvcrn-discovery)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.