Skip to content
Back to skills

Ideate

ASecurity

Internal methodology for the ideation discovery stage. Produces a concise Discovery Brief for downstream research, architecture, PRD, and planning.

  • 19 stars
  • 0 votes
  • 2 copies
  • 6 views
  • Added May 28, 2026
ai-agentsgo

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add GobbyAI/gobby --skill ideate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ideate?

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

Security grade badge for Ideate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gobbyai-ideate/badge)](https://www.skillsdirectory.com/skills/gobbyai-ideate)

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: ideate
description: Internal methodology for the ideation discovery stage. Produces a concise Discovery Brief for downstream research, architecture, PRD, and planning.
version: "1.0.0"
category: methodology
internal: true
triggers: ideation, discovery brief, problem framing
metadata:
  gobby:
    audience: agent
    depth: 0
---

# ideate - Discovery Brief Methodology

Use this skill when acting as the `analyst` discovery-stage agent.

## Purpose

Frame the work before evidence gathering. Convert the task description, user
context, existing labels, and any visible constraints into a short brief that
downstream stages can rely on.

## Method

1. Read the assigned task and existing discovery marker blocks.
2. Identify the real problem, not just the requested change.
3. Separate known constraints from assumptions.
4. State the most likely solution hypotheses without committing architecture.
5. Capture open questions only when answering them would change the work.

## Output

Write only this section shape:

```markdown
## Discovery Brief

### Problem
- <what needs to be solved>

### Constraints
- <known constraint>

### Hypotheses
- <testable direction>

### Open Questions
- <question or "None">
```

Keep the brief practical and evidence-seeking. Do not write implementation
tasks, PRD scope, architecture decisions, or planning manifests.

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.

Comments

Loading comments…

Newsletter

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