Add Issue

Goal

Create one durable, implementation-ready GitHub record per independently implementable item. Classify each item as Bug, Feature, or Task, establish all facts and decisions the implementer needs, and apply all clearly supported metadata that the current authenticated account is permitted to modify. Never implement the recorded work in the same invocation, including after a Plan Mode approval.

Deterministic Helpers

Use the self-contained helper contract and CLI for baseline capture/comparison, bounded GitHub observations, final payload and image validation, recording preflight, serialized writes, and result verification. The coordinator retains causal analysis, classification, semantic duplicate decisions, metadata selection, trusted authorization, repairs, and thread settlement. A helper's verified structure or a caller-supplied permission flag does not establish those judgments.

Run scripts/add-issue.mjs with Node.js and absolute JSON input paths. Keep private baselines, payloads and ledgers outside the investigated repository. Read the contract only for the active helper phase. Retain the exact final payload and its hash through delegation and continuation; mark a finalized Plan Mode payload with preparationMode: "plan". An approved-design handoff with no finalized payload follows the narrow fresh-preparation path below and produces a default-mode payload. Link bounded duplicate-review revisions through refresh only for payloads prepared outside Plan Mode, without discarding prior payloads or recording receipts. Use the dedicated recording subagent for record; Plan Mode and draft-only preparation use read-only commands. Never bypass a blocked or uncertain result with an ad hoc write. Follow the contract's receipt recovery or reserved native-browser operation without repeating completed writes.

T3 Runtime

Run this workflow in T3 Chat / T3 Code using the app-owned t3-code tools. Tool names may carry an MCP prefix such as mcp__t3_code__. Keep using the existing Node.js helpers for deterministic GitHub and workspace operations; they do not depend on the coordinating agent's provider.

• Read orchestrator_capabilities for the current provider/model catalog and interaction mode. Apply Plan Mode restrictions when that mode is plan; a draft-only request remains restrictive in every mode. Do not change modes or provider settings to bypass a restriction.
• Discover tools before declaring a capability unavailable. If the initial catalog omits T3 tools, make one direct mcp__t3_code__orchestrator_capabilities({}) attempt. If the runtime exposes T3_ACP_MCP_NODE but not callable MCP tools, use its supported acp-mcp-call transport with the same tool names and structured arguments. Do not substitute private app APIs.
• When browser evidence or a native GitHub attachment flow is necessary, prefer T3's collaborative browser. Call preview_status, then preview_open if no automation-capable tab is attached; inspect with preview_snapshot and use the focused interaction and preview_upload tools. Follow the runtime's tab ownership and browser fallback rules. T3 thread attachments are not GitHub-native issue attachments.