Skip to content

by Startups.Studio

Product Build and ship Issue

Issue.schedule

POST /{namespace}/issues/{issue}/schedule

Schedule commits an Issue to a week of work and records each scope change after the week starts.

Noun: Issue
Mode: do
Event: Issue.scheduled

You, to your agent

Schedule the latest issue.

curl -X POST https://api.sb/quietcopy.com/issues/issue_1/schedule \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week":"2026-10-22"}'

import { $ } from 'startup-builder'

const issue = await $.Issue.schedule({ issue: 'issue_1', week: '2026-10-22' })

npx startup-builder do Issue.schedule --json '{"issue":"issue_1","week":"2026-10-22"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Issue.schedule({ issue: 'issue_1', week: '2026-10-22' })"
  }
}

Inputs

Input	Type	Required	Description
`issue`	Issue	required	The Issue to commit.
`week`	`date`	required	The first day of the week it is committed to.

Outputs

Output	Type	Required	Description
`issue`	Issue	required	The scheduled Issue.

Effects

Emits Issue.scheduled.
Performed by the Product Lead.
Two-way: it runs at once, in the try, send and do modes.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Issue.schedule

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Issue.resolve

Previous Page

Issue.triage

Next Page