generate-behavior-questions

Generate Questions

Generate frame-specific clarifying questions for a feature by gathering all context (Jira, Confluence, Google Docs, Figma designs) and analyzing them comprehensively.

When to Use

Use when the user wants to:

• Review a feature's designs and generate clarifying questions
• Identify gaps, ambiguities, or contradictions in a feature spec
• Prepare for a feature review by listing what needs clarification

Typical trigger: "Generate questions for PROJ-123" or "What questions do we have about this feature?"

Required Input

• Jira issue key (e.g., PROJ-123) — the epic or story to analyze

Procedure

Phase 1: Fetch the Starting Issue

Call MCP tool extract-linked-resources with the Jira issue URL (e.g., https://myco.atlassian.net/browse/PROJ-123).

This returns the issue content as markdown with YAML frontmatter — save it directly to .temp/cascade/context/jira-PROJ-123.md.

The frontmatter contains discoveredLinks grouped by type (figma, confluence, jira, googleDocs) with relationship info (parent, blocks, etc.). Parse these to build your initial .temp/cascade/context/to-load.md.

If hasMoreComments: true, call again with commentsStartAt to get additional comment pages.

Phase 2: Iterative Content Loading

For each non-Figma URL in to-load.md (prioritize parent and blocks relationships first):

1. Call extract-linked-resources with the URL
2. Save the returned markdown to .temp/cascade/context/{type}-{identifier}.md
3. Parse discoveredLinks from frontmatter — add any new URLs to to-load.md
4. Repeat until no unloaded non-Figma URLs remain

Important: Figma URLs are collected but NOT loaded here — they go in the ## Figma section of to-load.md for Phase 3.

Phase 3: Figma Batch Load

For each Figma URL collected:

1. Call MCP tool figma-batch-zip with the Figma file URL
   • This returns a downloadUrl for a zip file and a manifest
2. Try to download and extract the zip:

   curl -sL "{downloadUrl}" -o /tmp/cascade-figma.zip && unzip -qo /tmp/cascade-figma.zip -d .temp/cascade/figma/ && rm /tmp/cascade-figma.zip
   

3. If curl succeeds (exit code 0), the extracted data is at:

   .temp/cascade/figma/{fileKey}/
   ├── manifest.json              ← frame list with metadata
   ├── prompts/
   │   └── frame-analysis.md      ← analysis prompt for frames
   └── frames/
       ├── {nodeId}-{name}/
       │   ├── image.png           ← frame screenshot
       │   ├── structure.xml       ← semantic component tree
       │   └── context.md          ← annotations/connections
       └── ...
   

   → Proceed to Phase 4 (filesystem path).