Update Ticket
Use this skill when a significant implementation or code-review milestone changes the
project's meaningful progress, or when the current ticket needs clarification. It is
for progress communication, not ticket workflow management.
Resolve every .agents/projects/ path from the repository root; never read or write
project artifacts in a global agent-installation directory.
Scope
This skill may draft and, after explicit user approval, perform only these updates:
- Add a Jira or GitHub comment.
- Update ticket descriptions when necessary to keep factual progress accurate.
- Update checklists in tickets or sub-tickets to reflect work that is actually done.
Ticket status, assignee, labels, relationships, estimates, priority, and every other
metadata field are outside this skill's scope. Implementation completion alone does
not establish ticket completion; user review, merge, tests, and other required
verification still govern it.
Process
Identify the active project and read .agents/projects/<project>/CONTEXT.md, LINKS.md,
todo.md, relevant spec, and the target Jira ticket or GitHub Issue. Inspect the
implementation and review evidence rather than inferring progress from intent.
Done when the ticket, current evidence, and unchanged metadata boundary are known.
Draft the smallest factual update needed. State completed behavior, verification
performed, known blockers, and next work only when evidence supports each claim.
Include proposed description or checklist changes separately from the comment.
End the proposed tracker comment with the exact line:
Written by Cursor
Done when the proposed update contains no unsupported completion claim or metadata
operation.
Show the user a concise summary of the proposed comment and any description or
checklist changes. Wait for explicit approval before modifying the tracker.
Done when the user approves the exact proposed tracker changes or declines them.
On approval, post only the approved comment, description, or checklist changes
through available Jira or GitHub tooling. If tooling is unavailable, provide the
ready-to-paste update and record the limitation in .agents/projects/<project>/todo.md.
Done when the approved update is posted or the ready-to-paste fallback is recorded.
Update the active project's context, links, and todo with the ticket URL, factual
progress, and remaining work. Do not mark the ticket complete unless the user has
confirmed all required review, merge, and verification conditions.
Done when project artifacts reflect the tracker update and its remaining work.
1---2name: update-ticket3description: Draft a Jira or GitHub progress update when meaningful implementation or review progress needs communicating, then post it only after user approval.4---56# Update Ticket78Use this skill when a significant implementation or code-review milestone changes the9project's meaningful progress, or when the current ticket needs clarification. It is10for progress communication, not ticket workflow management.1112Resolve every `.agents/projects/` path from the repository root; never read or write13project artifacts in a global agent-installation directory.1415## Scope1617This skill may draft and, after explicit user approval, perform only these updates:1819- Add a Jira or GitHub comment.20- Update ticket descriptions when necessary to keep factual progress accurate.21- Update checklists in tickets or sub-tickets to reflect work that is actually done.2223Ticket status, assignee, labels, relationships, estimates, priority, and every other24metadata field are outside this skill's scope. Implementation completion alone does25not establish ticket completion; user review, merge, tests, and other required26verification still govern it.2728## Process29301. Identify the active project and read `.agents/projects/<project>/CONTEXT.md`, `LINKS.md`,31 `todo.md`, relevant spec, and the target Jira ticket or GitHub Issue. Inspect the32 implementation and review evidence rather than inferring progress from intent.3334 Done when the ticket, current evidence, and unchanged metadata boundary are known.35362. Draft the smallest factual update needed. State completed behavior, verification37 performed, known blockers, and next work only when evidence supports each claim.38 Include proposed description or checklist changes separately from the comment.39 End the proposed tracker comment with the exact line:4041 ```text42 Written by Cursor43 ```4445 Done when the proposed update contains no unsupported completion claim or metadata46 operation.47483. Show the user a concise summary of the proposed comment and any description or49 checklist changes. Wait for explicit approval before modifying the tracker.5051 Done when the user approves the exact proposed tracker changes or declines them.52534. On approval, post only the approved comment, description, or checklist changes54 through available Jira or GitHub tooling. If tooling is unavailable, provide the55 ready-to-paste update and record the limitation in `.agents/projects/<project>/todo.md`.5657 Done when the approved update is posted or the ready-to-paste fallback is recorded.58595. Update the active project's context, links, and todo with the ticket URL, factual60 progress, and remaining work. Do not mark the ticket complete unless the user has61 confirmed all required review, merge, and verification conditions.6263 Done when project artifacts reflect the tracker update and its remaining work.
akathecoder