team-issueslisted

# Team Issues Import issues from a team tracker into your local backlog. Smart-splits multi-area issues into separate frontend/dev todos so each item maps cleanly to one skill pipeline. **Trigger**: `/team-issues`, `/team-issues <number>`, `/team-issues --mine`, `/team-issues --paste` ## Process > **Seed task list at start:** > > TaskCreate with phases: > > - PHASE 0: Pre-flight + tracker detection > - PHASE 1: Issue intake > - PHASE 2: Dedup + selection > - PHASE 3: Smart split analysis > - PHASE 4: User confirmation > - PHASE 5: Fragment confirm + checkpoint > - PHASE 6: Write to backlog > - PHASE 7: Output ### PHASE 0: Pre-flight + tracker detection > **Todo**: mark PHASE 0 → `in_progress`. 0. **Team-mode gate.** Read `.project/project.json#team.mode` (see `shared/PROJECT-MODE.md`). If `"solo"` or absent → show AskUserQuestion (warn-only): ```yaml header: "Solo project" question: "This project is marked solo (team.mode). /team-issues is meant for projects with multiple contributors. Continue anyway?" options: - label: "Cancel (Recommended)" description: "Exit. Toggle to team via the ⚙ button in the backlog or run /core-setup to mark this as a team project." - label: "Yes, continue once" description: "Proceed with issue import for this single invocation." multiSelect: false ``` Cancel → exit. Continue → proceed with PHASE 0 step 1. 1. Read `.project/project.json`: - Check `team.tracker` — if set, use that. - If no