OpenSpec Design Extension

Adds design asset integration to OpenSpec's proposal stage: when the user's prompt includes Figma links or images, fetch design data via the configured Figma MCP (tool names vary by server), save under openspec/changes/<change-id>/design/, and generate design/design-map.md.

Non-goals: Editing Confluence/wiki; writing to Figma.

Updating AGENTS.md on Execution

When the user invokes this skill, read the project's openspec/AGENTS.md and apply both updates below. OpenSpec templates differ by version—use the anchor lines to locate; if a section is missing, insert at the closest equivalent and keep numbering consistent.

1. Stage 1 workflow (numbered list under Creating Changes)

Anchor: Heading ### Stage 1: Creating Changes (or equivalent), then the line **Workflow** and the numbered list.

Change: After change-id and the change folder exist, add an explicit Design Extension step. Do not break apart a single “choose change-id and scaffold …” bullet into two bullets unless the template already does.