define-epics

Facilitate collaborative brainstorming to write numbered YAML epic-spec files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill define-epics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-epics
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/define-epics
Command: npx skills add https://github.com/lenlla/one_shot_build --skill define-epics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes friction from project kickoff by guiding collaborative brainstorming, capturing context, and converting conversations into ordered epic specifications so teams can move quickly from idea to execution.

Core Features & Use Cases

  • Guided Brainstorming: Opens with "What do you want to build today?" and drives a single-question-at-a-time conversation to elicit clear scope and priorities.
  • Context-aware Follow-ups: Reads provided context files (including data profiles), asks targeted data questions, and optionally searches shared knowledge to inform planning.
  • Structured Output: Writes numbered YAML epic spec files into kyros-agent-workflow/builds/<name>/epic-specs/ and commits them to the repository.
  • Use Case: During a data-science kickoff, use this Skill to gather requirements, inspect data profiles, and generate an ordered set of epics with acceptance criteria for model development.

Quick Start

Start a brainstorming session by asking what you want to build today and provide any context file paths or say none.

Frequently Asked Questions about define-epics

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

FAQPage Schema
How do I turn project vision into sequenced epics for predictive modeling?

Agile epic specifications are structured as numbered YAML files containing ordered tasks and acceptance criteria, written to a designated build directory and committed to the repository for team execution.

How do I start a brainstorming session to plan data-science project epics?

Context files, including data profiles, are read during project kickoff to inform targeted data questions, optionally search shared knowledge, and ensure generated epic specifications align with available data.

Can I use context files and data profiles to inform agile epic planning?

Yes, context files and data profiles are actively read during the brainstorming process to ask targeted data questions, search shared knowledge, and accurately inform the sequencing of agile project epics.

What is the best way to structure epic specifications in YAML for project planning?

The best way to structure epic specifications is generating numbered YAML files containing ordered epics and acceptance criteria, which are then written to a specific build directory and committed to the repository.

Does this agile epic generation process work without providing context files?

Yes, the brainstorming process works without context files by simply stating none when prompted, relying on interactive single-question conversations to capture project scope and generate ordered epics.