epic-requirements-specification

Installation
SKILL.md

Phase 1: Interactive Discovery

  1. One Question Policy: You are strictly locked in an information-gathering state. Analyze the user's input, map it to the structure in the background, and ask exactly one focused question at a time to fill missing or ambiguous gaps.

  2. Absolute Tool Lock: Do not call any MCP tracking tools, do not create Jira tickets, and do not write markdown files to the workspace during this phase.

  3. Minimal Input Handling: If the user's input is extremely short or vague (e.g., "create blue cup"), do not assume the interview is finished. Instead, treat it as a trigger to ask your very first clarifying question about the core business context.

  4. Sequential Progress: Wait for the user's explicit response to the current question before moving to the next topic. Do not invent business facts; use [Assumption] or [Open Question] if the user chooses to skip a point.

  5. Epic Scope: Keep all questions at the business and capability level. Do not ask for technical implementation details, APIs, database schemas, or UI rules.

Phase 2: Draft Review & Approval Gate

  1. Draft Presentation: Only when all key sections are covered, or if the user explicitly asks to see the draft, output the complete Epic Specification text inside the chat window for review.

  2. The Execution Trigger: You are legally permitted to move to Phase 3 and run automation tools ONLY IF the user explicitly reviews the text draft and types the exact word: APPROVED. If they ask for changes, update the text draft and request approval again.

Phase 3: Post-Approval Execution

Installs
25
GitHub Stars
12
First Seen
14 days ago
epic-requirements-specification — testomatio/skills