From cascade-mcp
Posts Figma frame-organized design behavior questions as a single structured markdown comment on a Jira issue using atlassian-add-comment MCP tool. Used after generate-behavior-questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cascade-mcp:cascade-post-design-questions-to-jiraThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Post behavior questions as a structured comment on the source Jira issue. All questions are combined into a single comment, organized by Figma frame with links.
Post behavior questions as a structured comment on the source Jira issue. All questions are combined into a single comment, organized by Figma frame with links.
Use after generate-behavior-questions has produced frame-specific questions and the user confirms they want to post them to Jira.
Typical trigger: User says "post to Jira" or "yes, add to PROJ-123" after reviewing generated questions.
generate-behavior-questions)PROJ-123) — the issue to comment onCombine all frame-specific questions into a single markdown comment:
## Behavior Questions
### [Login Screen](https://www.figma.com/design/abc123?node-id=1-234)
1. ❓ Should the "Remember me" checkbox be checked by default?
2. ❓ What error message appears for invalid credentials?
### [Dashboard](https://www.figma.com/design/abc123?node-id=5-678)
1. ❓ Is the widget layout user-configurable?
---
_Generated by Cascade feature review_
Formatting rules:
## Behavior Questions heading### [Frame Name](figma-url) — clickable link in JiraCall MCP tool atlassian-add-comment with:
issueKey: The Jira issue key (e.g., PROJ-123)markdownText: The formatted markdown commentThe tool handles markdown → ADF (Atlassian Document Format) conversion automatically.
Confirm to the user:
atlassian-add-comment tool accepts markdown and converts to ADF internallynpx claudepluginhub bitovi/cascade-mcp --plugin cascade-mcpConducts interactive one-at-a-time Q&A on Figma frame-specific design behavior questions, collects answers, and incrementally builds/updates a Q&A comment on a Jira issue.
Adds, lists, edits, or deletes comments on Jira issues via explicit /comment-jira-issue invocation. Requires user-provided body content and confirmation for write actions.
Fetches a JIRA issue and distills it into a structured task with acceptance criteria, sprint context, and codebase analysis. Surfaces missing criteria, scope, and risks, and can enrich the JIRA issue with analysis or spawn sub-tickets.