discover

Automate requirements discovery and acceptance-criteria derivation for new issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill discover-o3-ozono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/discover
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill discover-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams start new Issues by clarifying requirements and deriving acceptance criteria (Given/When/Then) before work begins, reducing ambiguity and rework.

Core Features & Use Cases

  • Session-start guard and structured outputs to capture requirements, ACs, and DoD in a standardized format.
  • Persona-aware user stories and acceptance criteria aligned with stakeholder goals.
  • End-to-end discovery workflow including DoD certification, risk checks, and plan-ready deliverables.

Quick Start

Invoke the discover skill to begin requirements exploration for a new Issue.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I derive acceptance criteria for new issues using Given When Then?

Automated requirements discovery applies Given/When/Then framing to generate three or more acceptance criteria for new issues. It enforces structured outputs including persona-aware user stories and a DoD checklist to reduce ambiguity.

What is the best way to automate requirements discovery for development and bug fixes?

Automated requirements discovery standardizes issue exploration by applying frontmatter-based capture and UX checks across development, bug fixes, refactoring, documentation, and research tasks to produce plan-ready deliverables.

Can I generate persona-aware user stories before starting issue management?

Yes, persona-aware user stories are generated during the discovery workflow to align acceptance criteria with stakeholder goals, ensuring the derived requirements match user expectations before development starts.

Does the requirements discovery workflow apply to documentation and research tasks?

The requirements discovery workflow applies to documentation and research tasks, enforcing structured frontmatter-based discovery and a DoD checklist to certify deliverables across all task types, not just development.

How do I enforce a definition of done checklist during issue discovery?

To enforce a definition of done checklist during issue discovery, the workflow applies DoD certification alongside risk checks and interruption checks, producing structured deliverables ready for stakeholder review.