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:
- Requirement understanding summary (1-2 paragraphs)
- User path/core interactions (list of steps)
- Draft Acceptance Criteria (AC): rewrite business statements into testable items
- List of implicit requirements (e.g. permissions, empty states, error states, performance/compatibility)
- Risks and uncertainties (questions requiring PM clarification, sorted by priority)
- 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:
- Read Story:
jira_get_issue - 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
- Get the Story Key
- Read and restate the requirement (to avoid misunderstanding)
- List uncertainties (one question at a time, prefer multiple-choice)
- Produce a structured summary (input for
aile-writing-plans)