gsd-to-linearlisted

# GSD to Linear Migration This skill reads a repo's `.planning/` directory and creates corresponding Linear issues for any incomplete work. It's a one-time migration — run it once per repo, then use the `linear-workflow` skill going forward. ## Command reference All linctl commands used by this skill are documented in `plugins/linear/LINCTL_REFERENCE.md`. Read it before running any linctl commands — it has exact flags and gotchas that prevent wasted calls. ## Before you start 1. Confirm linctl is authenticated: `linctl whoami` 2. Check that a `.planning/` directory exists in the current repo 3. Read `.planning/STATE.md` to understand where things stand 4. Discover the workspace: ```bash linctl team list --json linctl label list --team <TEAM_KEY> --json ``` If there's only one team, use it. If multiple, ask the user which one. ## What migrates (and what doesn't) **Migrates:** - Incomplete phases and their plans → Linear issues - PROJECT.md context → Linear project description - Phase-level acceptance criteria → issue descriptions - Requirements not yet satisfied → issue descriptions **Stays behind (already done, or not task data):** - Completed plans with SUMMARY.md files — these are history - STATE.md — Linear tracks state natively - config.json — agent execution settings, not task metadata - RESEARCH.md / CONTEXT.md — reference material, not actionable work - Completed milestones documented in MILESTONES.md — retrospectives, not tickets The goal is to move *remain