Start working on a task with full audit trail tracking. Creates or finds a ticket, sets status to in-progress, and tracks progress in comments. Use when asked to work on, fix, implement, or build something.
Begin tracked work on an issue with full audit trail.
If $ARGUMENTS looks like an issue ID (matches {PREFIX}-{slug}-{N} or legacy {PREFIX}-{N} pattern):
.project/issues/$1/issue.json to verify it exists.project/issues/$1/description.md for context.project/issues/$1/comments/ sorted by filename for historyIf $ARGUMENTS is a title (does not match an issue ID pattern):
.project/issues/*/issue.json for matching titles.project/config.json for prefix and team infoPROJECT_SLUG env var or config team array).project/counters/{slug}.json for next issue number (create with if missing){"nextId": 1}.project/issues/{PREFIX}-{slug}-{N}/issue.json with status "in-progress".project/issues/{PREFIX}-{slug}-{N}/description.md.project/counters/{slug}.jsonSet the issue status to in-progress and update the timestamp
Update issues index: Read .project/issues_index.json (create as [] if missing). Replace the entry with matching id (or add if missing) using fields: id, title, type, status, priority, assignee, labels, parent, created, updated. Sort by updated descending. Write back.
Add an opening comment:
{"id": "001", "author": "Claude Code", "content": "Starting work on this issue.", "created": "<ISO-8601>"}
Summarize the issue context to the user
Tell the user: "Tracking work under {ID}. I will add comments as I work and update the status when done."
As you implement changes, periodically add comments to the issue documenting:
review or donefeat(module): description [PREFIX-slug-N]