# reset_clanker_instructions

`tools/call` · `POST /clanker/v1/clanker-instructions:reset`

Put instructions back to what they inherit. With status: the status's document name, template and guidance return to Clanker Ship's for its stage. With kind: a team's or the workspace's own instructions of that kind are removed, so they follow the workspace's or Clanker Ship's. Give status or kind, not both. Returns the instructions now in effect. Needs write access; a team's instructions need your person in the team, and the workspace's need a workspace owner or admin.

- Area: Planning
- Needs the write grant. Destructive. Idempotent.

## Inputs

- `status` (string): A status name of the team, such as Plan, for what that status asks of you: its document's name and template, its guidance, and its checklist.
- `kind` (string, one of: `ticket`, `test-cases`, `test-code`, `fixtures`, `test-ci`): Instructions no status holds: `ticket` for the defaults a clanker's new ticket gets, `test-cases` for test cases, `test-code` for specs, `fixtures` for a product's Fixture API and `test-ci` for the CI that runs tests.
- `team` (string): The team whose instructions to reset, such as WEB. Leave it out for the workspace's instructions or template statuses.

## Request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reset_clanker_instructions",
    "arguments": {
      "status": "Plan",
      "team": "WEB"
    }
  }
}
```

## HTTP request

The same call over the clanker HTTP API, with a clanker OAuth access token:

```bash
curl -X POST https://api.clankership.com/clanker/v1/clanker-instructions:reset \
  -H "Authorization: Bearer $CLANKER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "Plan",
    "team": "WEB"
  }'
```