cascade-answer-design-questions-post-to-jira

Answer Design Questions — Post to Jira

Walk through design behavior questions one at a time, collecting answers from the user and building a growing Q&A comment on a Jira issue.

When to Use

Use after generate-behavior-questions has produced frame-specific questions and the user chooses to answer questions here and post Q&A to Jira.

Required Input

• Questions organized by Figma frame (output from generate-behavior-questions)
• Jira issue key (e.g., PROJ-123)

Procedure

1. Initialize tracking file

Create .temp/cascade/context/questions-answers-{issueKey}.md to track progress:

---
jiraIssueKey: PROJ-123
jiraCommentId: null
---

## Behavior Q&A

(Q&A pairs will be appended here as the user answers)

2. Flatten questions into ordered list

From the frame-organized questions, build a flat list preserving frame context:

Frame: Login Screen
  Q1: Should the "Remember me" checkbox be checked by default?
  Q2: What error message appears for invalid credentials?
Frame: Dashboard
  Q3: Is the widget layout user-configurable?

3. Ask each question

For each question, use the structured question UI (askQuestions in Copilot, AskUserQuestion in Claude Code) with suggested answer options.

Generate 2-4 suggested answers based on context from:

• The frame's analysis.md and context.md (Figma annotations, designer notes)
• Scope analysis findings
• Common UX patterns for the component type
• Any partial information from Jira/Confluence/Google Docs

Always include a "Skip" option.

Example:

header: "Question 1 of 5 — Frame: Case Details"
question: "The designer note says 'show 4 voters before +X others,' but the Text-Listing component only has 3 entry slots. Should the tooltip show a max of 3 or 4 voter names before truncating?"
options:
  - label: "Show 4 names (match designer note)"
    description: "Add a 4th entry slot to the component"
  - label: "Show 3 names (match current component)"
    description: "Update the designer note to match the XML structure"
  - label: "Skip"
allowFreeformInput: true

Ask one question at a time. Wait for the user's response before proceeding.

The user can select a suggested answer, type a custom response, or skip. All are valid.

4. After each answer — update Jira comment

Append the Q&A pair to .temp/cascade/context/questions-answers-{issueKey}.md:

### Login Screen

**💬 Should the "Remember me" checkbox be checked by default?**

A: Yes, checked by default for returning users. First-time visitors should see it unchecked.

Group consecutive questions under the same frame heading. Add a --- separator between frame sections.

Then post/update the Jira comment:

• First answer: Call atlassian-add-comment with the Q&A content (everything below the frontmatter ---). Save the returned commentId to the tracking file's frontmatter.
• Subsequent answers: Call atlassian-update-comment with commentId and the full updated Q&A content.

Always append a footer: _Generated by Cascade feature review — X/Y questions answered_

5. Completion summary

After all questions are answered (or skipped), report:

• Total questions answered / skipped / total
• Jira comment ID and issue key (with link)

Jira Comment Format

The growing Jira comment looks like:

## Behavior Q&A

### Login Screen

**💬 Should the "Remember me" checkbox be checked by default?**

A: Yes, checked by default for returning users.

**💬 What error message appears for invalid credentials?**

A: Show "Invalid email or password. Please try again." with a red banner.

---

### Dashboard

**❓ Is the widget layout user-configurable?**

A: Skipped

---

_Generated by Cascade feature review — 2/3 questions answered_

Important Notes

• One question at a time — never batch multiple questions in a single prompt
• Incremental posting — post/update after EACH answer, not at the end. Partial progress is saved if the session is interrupted.
• Comment ID tracking — the commentId from the first atlassian-add-comment call must be saved in the frontmatter and reused for all subsequent atlassian-update-comment calls
• Skip handling — if the user says "skip" or "I don't know", mark as "Skipped" in the Q&A document
• Read from tracking file — always read the current .temp/cascade/context/questions-answers-{issueKey}.md before updating, in case the user modified it manually