From datum-gtm
Quick-start feature discovery. Creates a pipeline entry and invokes the product-discovery agent to begin the discovery process.
How this skill is triggered — by the user, by Claude, or both
Slash command
/datum-gtm:discoversonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Shortcut to start feature discovery without manually creating pipeline artifacts.
Shortcut to start feature discovery without manually creating pipeline artifacts.
/discover <feature-description>
Feature description: $ARGUMENTS
Generate feature ID
.claude/pipeline/requests/ for existing IDsfeat-{NNN}Create request artifact
.claude/pipeline/requests/{id}-{slug}.mdInitialize pipeline state
.claude/pipeline/state/{id}.jsoncurrent_stage: "request"Invoke product-discovery agent
---
handoff:
id: feat-{NNN}
from: user
to: product-discovery
created: {timestamp}
context_summary: "{user's feature description}"
decisions_made: []
open_questions:
- "What problem does this solve?"
- "Who are the target users?"
assumptions: []
---
# Feature Request: {Feature Name}
**Requested by**: User
**Date**: {date}
## Initial Description
{User's feature description}
## Notes
This request is awaiting discovery. The product-discovery agent will:
- Clarify the problem being solved
- Identify target users
- Assess scope boundaries
- Evaluate platform capability requirements
- Produce a discovery brief
/discover VM snapshot management for compliance requirements
Creates:
.claude/pipeline/requests/feat-042-vm-snapshot-management.md.claude/pipeline/state/feat-042.jsonThen invokes product-discovery agent to begin discovery.
Created feature request: feat-042-vm-snapshot-management
Artifact: .claude/pipeline/requests/feat-042-vm-snapshot-management.md
Pipeline state: .claude/pipeline/state/feat-042.json
Starting discovery phase...
[Invokes product-discovery agent]
npx claudepluginhub datum-cloud/claude-code-plugins --plugin datum-gtmRuns the discovery phase of Hypo-Workflow planning: requirement clarification, constraint gathering, repo context analysis, and worker separation decisions. Use before decomposition.
Gathers structured requirements for new features through interactive WHO/WHAT/WHEN/WHY discussion, producing DISCOVERY artifact with features, NFRs, goals, anti-goals, references. Use when starting projects.
Dense execution-packet generator for goal clarification, product-fit pressure testing, and re-planning. Invoke to frame a problem, explore the problem space, and produce a structured discovery packet for downstream workflow steps.