Complete New Work

End-to-end Gyst delivery workflow for the workspace repo. Requires the gyst MCP server with a valid GYST_API_TOKEN.

Phase 1 — Discover open work

1. Call `get_projects_for_current_repo` (pass workspacePath if auto-detection fails).
2. If no projects or no repo detected, stop and tell the user to link the repo in Gyst or set GYST_WORKSPACE in ~/.cursor/mcp.json.
3. For each returned project, call `list_tickets` with that projectId.
4. Keep tickets where status !== "Completed".
5. Sort by ticketNumber ascending.
6. Present a table to the user:

| Key | Status | Title |
|-----|--------|-------|
| GYST-5 | Idea | ... |

Include project name(s) and ticketKeyPrefix context.

Phase 2 — Confirm before acting

Do not implement, commit, or push until the user confirms.

Ask the user to choose:

• Complete all listed tickets
• Complete specific ticket(s) only (user names keys)
• Cancel

If the list is empty, report that and stop.

Phase 3 — Per-ticket delivery loop

Process confirmed tickets one at a time.

3a. Read and start

1. `get_ticket_by_key` — read title, description, comments, commits, and project ticketStatuses.
2. `update_ticket_status` → In Progress (must be valid for the project).
3. `add_ticket_ai_dev_comment` — brief start comment: scope and planned approach.

3b. Implement and test

1. Implement only what the ticket requires; match existing codebase conventions.
2. Run relevant verification (build, tests, smoke scripts).
3. Fix failures before proceeding.

3c. Pre-ship ticket update

`add_ticket_ai_dev_comment` with Completed and Testing sections.

Do not set status to Completed yet if a commit is still required.

3d. Commit and push

Only when the user confirmed work in Phase 2:

1. Stage only relevant files.
2. Commit message must include the ticket key (e.g. GYST-4: Expand MCP tooling.) so dev-link sync works.
3. Push to main.
4. Note the full commit SHA.

3e. Close and link

1. `add_ticket_ai_dev_comment` — shipped note with commit SHA.
2. `update_ticket_status` → Completed
3. `sync_ticket_dev_links` with ticketId

MCP quick reference

Server: `gyst` in Cursor MCP config. Generate token at Gyst → Settings → Cursor MCP.