todos-to-github-project

# Todos to GitHub project Goal end-state: every remaining todo of the conversation is one task-spec issue, the issues sit in one GitHub project, every dependency is a blocked-by edge on GitHub, and each in-scope issue carries `ready-for-agent`. The issue format — title, body sections, the `ready-for-agent` bar — is defined in [docs/authoring/github-issues.md](../../../docs/authoring/github-issues.md) and [docs/authoring/github-issues-task-spec.md](../../../docs/authoring/github-issues-task-spec.md). Prose in titles and bodies follows [docs/authoring/WRITING.md](../../../docs/authoring/WRITING.md). This skill covers what to file, in which order, and with which `gh` calls. ## 1. Harvest 1. Collect every remaining todo from the conversation: open task-list items, deferred follow-ups, and work the user parked for later. 2. Search the tracker for each todo with `gh issue list --search "<keywords>"`. If an existing issue already tracks it, drop the todo from the set. 3. Write one sentence per todo stating the outcome its issue must deliver. If the sentence only makes sense with the conversation open, ask the user what the todo means. ## 2. Draft 1. Name the project after the outcome the set delivers, not after the conversation. 2. Split the todos into in-scope and out-of-scope. An out-of-scope todo files under its issue type with the type label, stays out of the project, and never carries `ready-for-agent`. 3. Draft each in-scope issue as a task spec in the github-issues-task...