[v2.0] GSD/BMAD/Superpowers compatibility layer — clean spec handoff format

[FredAntB]

Context

Discord beta feedback raised a valid point: the skill generates spec files
but doesn't define how those files hand off to execution frameworks like
GSD, BMAD, or Superpowers. Developers using those frameworks still need a
spec layer — that's our gap to fill.

Goal

Define a handoff format that lets requirements.md, design.md, and tasks.md
feed directly into GSD, BMAD, and Superpowers without manual reformatting.

Proposed work

• Research GSD's input format — what structure does it expect for tasks
  and requirements?
• Research BMAD's PRD and architecture doc conventions — can our
  requirements.md and design.md map to them directly?
• Research Superpowers' Spec phase — what does it consume?
• Add a ## Handoff section to tasks.md template with execution-framework
  compatible output
• Add README section: "Using with GSD / BMAD / Superpowers" positioning
  this skill as the spec layer in a larger stack
• Add Phase 2A assertions for handoff section presence in tasks.md template

Success condition

A developer using GSD can take the output of this skill and feed it into
GSD's execution phase without any manual reformatting.

References

• https://github.com/taches-app/gsd (GSD)
• Discord feedback thread (beta issue [beta-friction] Discord feedback — skill scope vs full workflow orchestration #5 ])