Slash Command

/SKILL

Updates a project state field via TeamMCP with new value and reason, verifies the change, and handles approval flow if not the owner.

developer-tools

npx claudepluginhub cookjohn/teammcp

Details

Namespaceskills/update-state/

Allowed Tools

mcp__teammcp__get_statemcp__teammcp__set_statemcp__teammcp__request_approvalmcp__teammcp__get_pending_approvalsmcp__teammcp__send_dmmcp__teammcp__send_message

Prompt Preview

# Update Project State

## Instructions

1. **Parse arguments**
   - Extract from `$ARGUMENTS`:
     - `project_id` — the project identifier
     - `field` — the state field to update
     - `value` — the new value to set
     - `reason` — why this change is being made
   - If any required parameter is missing, ask the user to provide it.

2. **Check current state**
   - Call `get_state` with the `project_id` to read the current value of the field.
   - Log the current value for reference before making changes.

3. **Attempt to set state**
   - Call `set_state` with `project_id`, `field`, `...

Command Content

Other plugins with /SKILL

/update-status

1.0k

Updates Linear ticket status and progress: sets backlog/todo/in-progress/in-review/done/cancelled, adds comments, links PRs, syncs sub-tasks, notifies team, updates estimates/cycles, reports changes.

linear-helper

/update

Updates task status, fields, scope, tags, dependencies, position, and milestones. Supports batch updates, AI rewrites via prompts, validation, and milestone creation.

2 tools

taskmanager

/team-update

689

Posts project updates to team chat, gathers and triages feedback via modes: update (full cycle), standup, check, feedback, plan.

1 tool

dev-tools

/update-issue

Updates status of specified issue (e.g., 'In Progress', 'Code Review') in configured Linear or Jira system using state management file. Outputs confirmation.

claude-constructor

/issue-update

104

Updates existing tickets/issues with status changes, comments, assignees, labels, priority, milestones, or other fields using configured provider. Returns confirmation and updated details.

sonnet6 tools

sdlc

/pac-update-status

2.7k

Updates PAC ticket status in .pac/tickets/ YAML files, validates transitions, updates assignee/comments/tasks, tracks progress, syncs epics.

2 tools

all-commands

Stats

Stars37

Forks3

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Update Project State ## Instructions 1. **Parse arguments** - Extract from `$ARGUMENTS`: - `project_id` — the project identifier - `field` — the state field to update - `value` — the new value to set - `reason` — why this change is being made - If any required parameter is missing, ask the user to provide it. 2. **Check current state** - Call `get_state` with the `project_id` to read the current value of the field. - Log the current value for reference before making changes. 3. **Attempt to set state** - Call `set_state` with `project_id`, `field`, `...

Update Project State

Instructions

Parse arguments

Extract from $ARGUMENTS:
- project_id — the project identifier
- field — the state field to update
- value — the new value to set
- reason — why this change is being made
If any required parameter is missing, ask the user to provide it.

Check current state

Call get_state with the project_id to read the current value of the field.
Log the current value for reference before making changes.

Attempt to set state

Call set_state with project_id, field, value, and reason.
If the call succeeds, proceed to verification.

Handle approval flow (if needed)

If set_state fails due to ownership or permission restrictions:
- Call request_approval to submit the state change for approval.
- Notify the state owner via send_dm that an approval is pending.
- Report to the user that the change requires approval and is pending.
- Stop here — do not retry.

Verify the update

Call get_state again with the same project_id and confirm the field now holds the new value.
Report success with both the old and new values.

Notify if appropriate

If the state change is significant (e.g., status transitions like "in-progress" to "done"), send a notification to the relevant channel via send_message.

$ARGUMENTS

/update-state <project_id> <field> <value> <reason>

Example: /update-state proj-123 status in-review "Feature implementation complete, ready for review"

Update Project State

Instructions

Parse arguments
- Extract from $ARGUMENTS:
  - project_id — the project identifier
  - field — the state field to update
  - value — the new value to set
  - reason — why this change is being made
- If any required parameter is missing, ask the user to provide it.
Check current state
- Call get_state with the project_id to read the current value of the field.
- Log the current value for reference before making changes.
Attempt to set state
- Call set_state with project_id, field, value, and reason.
- If the call succeeds, proceed to verification.
Handle approval flow (if needed)
- If set_state fails due to ownership or permission restrictions:
  - Call request_approval to submit the state change for approval.
  - Notify the state owner via send_dm that an approval is pending.
  - Report to the user that the change requires approval and is pending.
  - Stop here — do not retry.
Verify the update
- Call get_state again with the same project_id and confirm the field now holds the new value.
- Report success with both the old and new values.
Notify if appropriate
- If the state change is significant (e.g., status transitions like "in-progress" to "done"), send a notification to the relevant channel via send_message.

$ARGUMENTS

/update-state <project_id> <field> <value> <reason>
Example: /update-state proj-123 status in-review "Feature implementation complete, ready for review"