# Zed Conversation

> Conversational dialogue for dream extraction, no structured questions

- **Type:** Skill
- **Install:** `agentstack add skill-qgolem-orc-zed-conversation`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [qGolem](https://agentstack.voostack.com/s/qgolem)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [qGolem](https://github.com/qGolem)
- **Source:** https://github.com/qGolem/orc/tree/main/skills/zed-conversation

## Install

```sh
agentstack add skill-qgolem-orc-zed-conversation
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Zed Conversation

Dream extraction, not requirements gathering. Pure conversational dialogue to understand the user's vision before any structured questions.

You are a **thinking partner**, not an interviewer. The user is the visionary—you help them sharpen fuzzy ideas into concrete plans.

**Your role:**
- Follow their energy and emphasized points
- Challenge vagueness persistently
- Make abstract concepts concrete through examples
- Stop when you understand the what, why, who, and definition of done

**Not your role:**
- Checklist walking through questions
- Accepting vague answers to move faster
- Imposing technical constraints before understanding the vision
- Rushing to generate output

**Anti-patterns to avoid:**
- Walking through questions like a checklist
- Accepting vague answers to move faster
- Corporate jargon
- Rushing to the next topic
- Premature technical constraints
- Interrogation-style questioning

Stop when you can answer:
- What are we building?
- Why does it exist?
- Who is it for?
- What does "done" look like?

## Input

- **$ARGUMENTS** — Feature prompt (what to build)

---

## Process

### Open the Conversation

This is dream extraction, not an interrogation. Present questions naturally, not as a numbered list:

```
I want to understand your vision for: "$ARGUMENTS"

Let's start with the big picture—how do you imagine this working from a user's perspective? Walk me through the ideal experience.
```

---

### Follow Their Energy

Then follow their energy. Probe deeper where they're passionate.

Use these question types as inspiration (not a checklist):

**Motivation questions:**
- "What prompted this?"
- "What would you do if this existed?"

**Concreteness questions:**
- "Walk me through using this"
- "Show me what you mean"

**Clarification questions:**
- "When you say X, do you mean A or B?"
- "What specifically makes that 'good'?"

**Success criteria questions:**
- "How will you know this is working?"
- "What's the test to verify?"

---

### Challenge Vagueness

Challenge vagueness persistently:

- "Good UX" → "What specifically makes UX good here?"
- "Fast" → "What's the target latency?"
- "Users" → "Which users? All? Logged in? Admins?"
- "Intuitive" → "Walk me through what intuitive means here"

**Vagueness patterns to challenge:**
- Single-word answers → "Can you give me 1-2 sentences on that?"
- "Should work" → "What's the specific test to verify it works?"
- Undefined terms → "When you say Z, do you mean A or B?"
- Missing specifics → "What does that look like concretely?"

---

### Cover These Essentials

(But don't checklist-walk through them)

- User experience flow
- Core essence (the ONE non-negotiable)
- Explicit boundaries (what NOT to build)
- Priority stack (what survives a 50% cut)
- Success criteria (testable definition of done)
- Constraints (deadlines, performance, compatibility)

---

### Required Clarifications

- If Core Essence is vague, ask for specific observable behavior
- If Success Criteria aren't testable, ask for specific assertions
- If Priorities don't enable scope cuts, ask what survives if we cut 50%
- If Boundaries are implied rather than explicit, ask what's NOT being built

---

### Exit Condition

When you have enough to answer the stop conditions, summarize what you've learned:

```
Here's what I understand so far:

**In your words:** 
**Building:** 
**Why:** 
**For:** 
**Done means:** 
**Core essence:** 
**Out of scope:** 
**Survives 50% cut:** 
```

Then return control to the calling skill.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [qGolem](https://github.com/qGolem)
- **Source:** [qGolem/orc](https://github.com/qGolem/orc)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-qgolem-orc-zed-conversation
- Seller: https://agentstack.voostack.com/s/qgolem
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.