# To Issues

> Preserve plans, findings, or follow-up work as actionable issue records. Use when deferred work needs local tracking or the user authorizes synchronization to an external tracker.

- Skill: `typeweaver/to-issues` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add typeweaver/to-issues`
- Raw SKILL.md: https://api.skillmd.com/api/skills/typeweaver/to-issues/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: typeweaver (https://skillmd.com/u/typeweaver)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/typeweaver/to-issues

---


# To Issues

Preserve actionable work without expanding the current implementation.

## Choose the destination

- **Local by default:** Follow an existing repository convention. Otherwise
  write one Markdown file per independent outcome under `docs/issues/` using
  [assets/issue-template.md](assets/issue-template.md). Local records need no
  separate external authorization when repository changes are already approved.
- **External when authorized:** Create tracker issues only after explicit user
  authorization. Reuse local records or plans as the source instead of drafting
  competing descriptions.
- **Response fallback:** When repository writes are not authorized or no
  workspace exists, return issue drafts without creating files.

## Process

1. Read the relevant plan, conversation, PR, findings, code, and existing issue
   records.
2. Keep work in the current change when it is required for correctness or the
   agreed outcome. Record only genuinely deferred work.
3. Split records by independently deliverable outcome. Keep related tasks
   together when separating them would lose necessary context.
4. Capture the reason, goal, observable completion criteria, and only the
   references needed to resume the work.
5. Link the originating plan, pull request, review, or issue when available.

When synchronizing a plan, keep the durable plan as the technical source of
truth. Create a concise tracker issue that explains the outcome and links the
plan. For a roadmap, create an umbrella issue and separate issues only for
independently executable milestones.

Do not invent requirements, labels, priorities, owners, or implementation
details unsupported by the source context. Do not add status or date ceremony
unless the repository already requires it.

## Report back

Report created local paths and external issue links. Distinguish local records
from published tracker items and state any item that could not be created.