External-tracker mode publishes project planning details to a third-party account
Source references: 3When the user or project rules designate GitHub, Jira, Linear, or another tracker, the instructions require creating an external item for every task. Item bodies include descriptions, acceptance criteria, verification steps, and dependencies, which can reveal unreleased features, file locations, or architecture details.
Project information may leave the local workspace and become visible according to the destination project's permissions, potentially to an organization or the public. Persistent records are also created in the user's account.
This is not a hidden upload to an arbitrary third party. The skill creates tracker items only when the user or project rules have already designated an external tracker, and it explicitly states that acceptance criteria, verification steps, and dependencies go into those items. That is a normal, conditional output of a planning skill. Items may also include likely file paths, so the tracker's visibility matters, but the source does not show bypassing authorization, choosing an undesignated account, or making content public on its own.
This assessment concerns the code and conditions shown, not proof that harm has occurred.Each task follows this structure, whether it lands in the markdown task list or as an item in an external tracker (see Output Files):```markdown## Task [N]: [Short descriptive title]**Description:** One paragraph explaining what this task accomplishes.**Acceptance criteria:**- [ ] [Specific, testable condition]- [ ] [Specific, testable condition]**Verification:**- [ ] Tests pass: [the repository's focused-test command]- [ ] Build succeeds: [the repository's build command]- [ ] Manual check: [description of what to verify]**Dependencies:** [Task numbers this depends on, or "None"]**Files likely touched:**- `src/path/to/file.ts`- `tests/path/to/test.ts`**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]```Show 2 other places
- **Default: a checklist-style markdown file at `tasks/todo.md`.** This is the convention the `/build` command and other downstream tooling expect. Use it unless the project says otherwise.- **External tracker:** if the project's agent rules (`CLAUDE.md`, `AGENTS.md`, etc.) or the user designate an issue tracker (e.g. GitHub Issues, Jira, Linear, `bd`/beads), create one tracker item per task instead of writing `tasks/todo.md`. Map the Step 4 structure onto the tracker's fields: acceptance criteria and verification steps in the item body, dependencies via the tracker's linking mechanism (`bd dep add`, "blocked by", etc.). Record Step 5 checkpoints as tracker items too, or as a checklist in the plan document if the tracker has no natural equivalent.When using an external tracker, note it in `tasks/plan.md` (e.g. "Tasks tracked in Linear project FOO") so downstream steps and future sessions know where to look, and keep the plan document's Task List section as an ordered index of tracker item IDs or links rather than a duplicate checklist.- **Default: a checklist-style markdown file at `tasks/todo.md`.** This is the convention the `/build` command and other downstream tooling expect. Use it unless the project says otherwise.- **External tracker:** if the project's agent rules (`CLAUDE.md`, `AGENTS.md`, etc.) or the user designate an issue tracker (e.g. GitHub Issues, Jira, Linear, `bd`/beads), create one tracker item per task instead of writing `tasks/todo.md`. Map the Step 4 structure onto the tracker's fields: acceptance criteria and verification steps in the item body, dependencies via the tracker's linking mechanism (`bd dep add`, "blocked by", etc.). Record Step 5 checkpoints as tracker items too, or as a checklist in the plan document if the tracker has no natural equivalent.When using an external tracker, note it in `tasks/plan.md` (e.g. "Tasks tracked in Linear project FOO") so downstream steps and future sessions know where to look, and keep the plan document's Task List section as an ordered index of tracker item IDs or links rather than a duplicate checklist.