SuperAPI AI Directory

aile-requirement-intake

General & other

View repository

Updated 10-16 08:49

About this skill

Aile: Requirement Intake (aile-requirement-intake)

Overview

This skill is used for the first step of Phase 2: converting the inputs of a Jira Story (requirement description, UI mockups, constraints) into structured material that can be used for planning and design.

Source Original Skill

  • Source:skills/brainstorming/SKILL.md
  • Strategy: Keep the original Skill as the baseline and fallback path; this Skill is copied and rewritten to add Jira input parsing and team output format.

Input

  • Jira Story: Description, Acceptance Criteria (if any), attachments/links (UI mockups) - (Optional) related Epic / dependent Story

Output (requirement intake summary)

The following structure must be output:

  1. Requirement understanding summary (1-2 paragraphs)
  2. User path/core interactions (list of steps)
  3. Draft Acceptance Criteria (AC): rewrite business statements into testable items
  4. List of implicit requirements (e.g. permissions, empty states, error states, performance/compatibility)
  5. Risks and uncertainties (questions requiring PM clarification, sorted by priority)
  6. Suggested next step for Phase 2: whether Pencil design is needed, whether subtasks need to be split

Jira MCP (optional)

If the environment provides a Jira MCP Tool (e.g. mcp-atlassian), perform the following steps:

  1. Read Story:jira_get_issue
  2. Write the "requirement intake summary" into the Comment:jira_add_comment

Note: Credentials (API Token) must be injected via environment variables and must not be written into the repository.

Execution flow

  1. Get the Story Key
  2. Read and restate the requirement (to avoid misunderstanding)
  3. List uncertainties (one question at a time, prefer multiple-choice)
  4. Produce a structured summary (input for aile-writing-plans )