What problem does it solve? When many ideas and requests pile up, it becomes hard to keep each piece of work isolated, trackable, and verifiable. This Skill turns a pinned Codex Intent intake thread into a thin front desk that converts each user input into exactly one new Codex task per deliverable, so work stays separated and results remain pinned for human review. ## Core Features & Use Cases - Intent Routing: Interprets each user input in the intake thread and creates a new Codex task titled TNNN · deliverable name with a structured initial prompt. - Project and Environment Selection: Chooses the primary project (projectless, codex-agent-ops, or the owning repository) and decides between Local and Worktree execution based on conflict and isolation rules. - Numbering and Intake Rotation: Manages reserved 15-task numbering ranges, pins created tasks, and replaces the intake thread when its range is exhausted or consistency degrades. - Use Case: You pin a Codex Intent 受付 · T028–T042 thread, send it a request like "add dark mode to my settings page", and it creates a pinned T028 · add dark mode task in the right project with a complete initial prompt, without doing the implementation itself. ## Quick Start Invoke $codex-intent in a pinned intake thread and send your request so it creates one new pinned Codex task for that deliverable.
