deliver

name	deliver
description	Take a request — a Linear issue or a feature description — all the way to a reviewed, ready PR: triage it, work out the right approach, propose it for a quick OK, implement, then ship. Use when the user wants the agent to plan and build something end to end.

Deliver

From a request to a reviewed PR. Do the thinking yourself — work out the right approach and propose just that one; offer alternatives only when the choice is genuinely underdetermined. The user weighs in twice, lightly: on the proposal and on the finished work. Work in a git worktree if you're on a shared checkout — git worktree add a branch, then copy the repo-root .env into it and symlink the repo-root .settings/ so ct and environments resolve.

1. Ingest — given a Linear issue, read it and the context around it: linked issues, the broader project it belongs to, to the appropriate depth. Given only a description, create a Linear issue for it, tagged agent-made so it's filterable. Either way you now have an issue to track through the lifecycle.
2. Triage — decide if it's worth doing now, and stop unless it is: already done → comment with the pointer and leave the status alone; stale or wrong → propose closing; underspecified → flag it. Mark survivors In Progress.
3. Investigate — understand it deeply: the code, related PRs, external context, whatever bears on the right approach.
4. Propose — write a single, clean, easy-to-read proposal for the approach you judge best. Ask the user to confirm it, recommended path first; add alternatives as options only when there's no clear winner.
5. Implement the approved approach, simplifying as you go.
6. Confirm — show the result, ask if it looks good, then run /ship.
7. Close the loop — update the Linear issue: In Review, PR link. Never mark a real issue Duplicate.