discovery

Convert topics into structured backlog tickets and research artifacts.

1|Updated Apr 1, 2026

Search Tags:#workflow #planning #discovery #epics #backlog #tickets

Ready to run

npx skills add https://github.com/charleshall888/cortex-command --skill discovery-charleshall888

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-core/skills/discovery
Command: npx skills add https://github.com/charleshall888/cortex-command --skill discovery-charleshall888

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ideation and planning often stall at the gap between understanding a topic and writing actionable backlog tickets. This skill guides teams from clarifying a topic through research and finally to concrete backlog items grouped by epic.

Core Features & Use Cases

Clarify → Research → Decompose workflow that converts vague topics into a structured backlog pipeline.
Artifact preservation: persists research artifacts and generates backlog items with standard frontmatter for lifecycle integration.
Project-root guidance: ensures commands run from project root and outputs to cortex/backlog and cortex/research.

Quick Start

Invoke the discovery skill on a topic using the /cortex-core:discovery command to begin clarify and decompose into backlog tickets.

Frequently Asked Questions about discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn vague project topics into actionable backlog tickets?▼

To turn vague topics into backlog tickets, you need a structured discovery workflow that clarifies the topic, performs sizing research, and decomposes outcomes into epics. This bridges the gap between ideation and planning.

What is the best way to structure ideation and planning before writing backlog tickets?▼

The best way to structure ideation is using a clarify, research, and decompose pipeline. This approach converts unclear topics into structured discovery artifacts, ensuring backlog items are well-formed and grouped by epic.

How do I generate epics and backlog tickets from a project topic?▼

You generate epics and backlog tickets by initiating a discovery process on your topic. This automates topic-clarity checks, handles sizing research, and breaks down outcomes into structured backlog items with standard frontmatter.

Do I need a specific project structure to generate and persist backlog artifacts?▼

Yes, you need a project-root workflow environment to generate and persist backlog artifacts. The discovery process enforces running commands from the project root and outputs research and backlog files to dedicated directories.

How are research artifacts preserved for lifecycle integration?▼

Research artifacts are preserved by persisting them within structured project directories and generating backlog items with standard frontmatter. This ensures outputs are saved for lifecycle integration and downstream planning.