DigitalStack Developers
Sign inGet API keys

Capabilities

Work Item Enhance

Create proposal-first enhancement runs over canonical work items: requirements, description drafts, design notes, implementation plans, acceptance criteria, test plans, estimates, and risk checks.

Interfaces

RESTAvailable

Proposal-first runs, drafts, artifacts, explicit apply, and operation status are available through REST.

MCPAvailable

MCP tools now cover the full Work Item Enhance runtime: list, create, retrieve, run actions, inspect drafts/artifacts, operation status, prepare apply, and apply selected drafts.

GraphQLAvailable

GraphQL can create runs, run named actions, list/retrieve runs, filter drafts/artifacts, and apply selected drafts through the same service and scopes as REST.

WebhooksAvailable

Six lifecycle events are emitted through the durable webhook outbox for queued, action-completed, draft-created, completed, applied, and failed facts.

Required scopes

work-item-enhance:runAPI key scoperequired
Create proposal-first Work Item Enhance runs and execute bounded enhancement actions.
work-item-enhance:readAPI key scoperequired
Read Work Item Enhance runs, generated drafts, artifacts, evidence references, and apply history.
work-item-enhance:applyAPI key scoperequired
Apply selected Work Item Enhance drafts back to authorized canonical work-item fields.
work-item-enhance:code-contextAPI key scoperequired
Inspect authorized repository/code context for Work Item Enhance implementation planning without writing code.

Examples

Create a Work Item Enhance run — view in REST API reference

curl -X POST "https://www.digitalstack360.com/api/v1/work-item-enhancements" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Idempotency-Key: enhance-work-42-v1" \
  -H "Content-Type: application/json" \
  -d '{"target":{"type":"work_item","id":"work_01k2..."},"actions":["requirements","description","implementation_plan","acceptance_criteria"],"instructions":"Prepare this for an engineer to start tomorrow.","confirm":true}'

List Work Item Enhance runs — view in REST API reference

curl -X GET "https://www.digitalstack360.com/api/v1/work-item-enhancements" \
  -H "Authorization: Bearer $DS_API_KEY"

Retrieve a Work Item Enhance run — view in REST API reference

curl -X GET "https://www.digitalstack360.com/api/v1/work-item-enhancements/wie_01k6..." \
  -H "Authorization: Bearer $DS_API_KEY"

Run a Work Item Enhance action — view in REST API reference

curl -X POST "https://www.digitalstack360.com/api/v1/work-item-enhancements/wie_01k6.../actions" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Idempotency-Key: enhance-action-work-42-design" \
  -H "Content-Type: application/json" \
  -d '{"action":"design","instructions":"Include API boundary notes.","confirm":true}'

List Work Item Enhance drafts — view in REST API reference

curl -X GET "https://www.digitalstack360.com/api/v1/work-item-enhancements/wie_01k6.../drafts" \
  -H "Authorization: Bearer $DS_API_KEY"

List Work Item Enhance artifacts — view in REST API reference

curl -X GET "https://www.digitalstack360.com/api/v1/work-item-enhancements/wie_01k6.../artifacts" \
  -H "Authorization: Bearer $DS_API_KEY"

Apply selected Work Item Enhance drafts — view in REST API reference

curl -X POST "https://www.digitalstack360.com/api/v1/work-item-enhancements/wie_01k6.../apply" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Idempotency-Key: apply-work-42-enhancement-v1" \
  -H "Content-Type: application/json" \
  -d '{"draft_ids":["draft_01k6..."],"expected_target_version":"2026-07-15T14:22:04Z","confirm":true}'

Get Work Item Enhance operation status — view in REST API reference

curl -X GET "https://www.digitalstack360.com/api/v1/operations/wie_01k6..." \
  -H "Authorization: Bearer $DS_API_KEY"
“List enhancement runs for this work item.”
“Enhance this work item for engineering readiness, then show me the generated drafts before applying anything.”
“Show me this enhancement run and the drafts ready for review.”
“Show me the current operation status for this enhancement run.”
“Run the implementation-plan action for this enhancement run after I confirm.”
“Draft requirements for this enhancement run and call out unresolved assumptions.”
“Rewrite this work item description so an engineer can start without ambiguity.”
“Draft a lightweight design note for this work item.”
“Show me the likely files and tests for this enhancement run, plus anything still missing.”
“Show me the applyable drafts for this enhancement run.”
“Show me the review artifacts for this enhancement run.”
“Prepare the apply package for these selected drafts and show the field-level diff for confirmation.”
“Apply these selected drafts after I review the diff and explicitly confirm.”

GraphQL examples

Create an enhancement runAvailablework-item-enhance:run

Create a proposal-first run. Drafts and artifacts are returned for review; the work item is not changed.

mutation CreateWorkItemEnhancementRun($input: CreateWorkItemEnhancementRunInput!) {
  createWorkItemEnhancementRun(input: $input) {
    ok
    idempotencyReplayed
    run {
      id
      state
      target { id key title version }
      requestedActions
      drafts {
        id
        action
        field
        proposedValue
        applyEligible
      }
      artifacts {
        id
        type
        title
        summary
      }
    }
    errors { code message path }
  }
}
Read a run and review applyable draftsAvailablework-item-enhance:read

Fetch the generated drafts/artifacts and the target version required by an apply command.

query WorkItemEnhancementRun($id: ID!) {
  workItemEnhancementRun(id: $id) {
    id
    state
    target { id key title version }
    drafts {
      id
      action
      field
      proposedValue
      confidence
      evidenceRefs { kind id }
      applyEligible
    }
    artifacts {
      id
      type
      title
      summary
      evidenceRefs { kind id }
    }
    allowedActions { id label requiredScope }
  }
}
Filter generated draftsAvailablework-item-enhance:read

Read only applyable description drafts before asking a user which draft to apply.

query EnhancementDrafts($runId: ID!) {
  workItemEnhancementDrafts(runId: $runId, field: "description", applyEligible: true) {
    id
    action
    field
    proposedValue
    confidence
    evidenceRefs { kind id }
  }
}
Apply selected draftsAvailablework-item-enhance:apply

Apply selected field drafts after user confirmation. The mutation uses the same explicit target-version guard as REST.

mutation ApplyWorkItemEnhancementDrafts($input: ApplyWorkItemEnhancementDraftsInput!) {
  applyWorkItemEnhancementDrafts(input: $input) {
    ok
    run {
      id
      state
      appliedDraftIds
      target { id key title version }
    }
    errors { code message path }
  }
}

Webhook emits

work_item_enhancement.queuedAvailable

A Work Item Enhance run was accepted and queued.

Resource: work_item_enhancement_run

run_idtarget_typetarget_idrequested_actionsqueued_at
work_item_enhancement.action_completedAvailable

One enhancement action completed and produced drafts or artifacts.

Resource: work_item_enhancement_run

run_idactiondraft_idsartifact_idscompleted_at
work_item_enhancement.draft_createdAvailable

A field-level draft was created for review.

Resource: work_item_enhancement_run

run_iddraft_idfieldtarget_idcreated_at
work_item_enhancement.completedAvailable

The enhancement run finished and is ready for review.

Resource: work_item_enhancement_run

run_idtarget_iddraft_countartifact_countcompleted_at
work_item_enhancement.appliedAvailable

Selected drafts were applied to the canonical work item.

Resource: work_item_enhancement_run

run_idtarget_idapplied_draft_idstarget_versionapplied_at
work_item_enhancement.failedAvailable

The run or action failed with a durable error code.

Resource: work_item_enhancement_run

run_idactionerror_codefailed_at

All webhook events use the shared v1 envelope, signed delivery, and minimal payload rule. Fetch by resource id for expanded data.

System boundaries

Systems commonly integrated with this capability. Each row states the boundary and its native status; it does not transfer canonical authority to the connected system.

DigitalStack owns

  • • Enhancement run identity, requested actions, state, evidence references, drafts, artifacts, and apply history
  • • Canonical Execute work-item fields changed only by an explicit apply command
  • • Webhook facts for enhancement lifecycle transitions

Source systems own

  • • External repository contents until a governed code-context connector is authorized
  • • Provider-native issue fields unless mapped to canonical Execute work items
  • • Human approval of generated requirements, design, and implementation plans

Typical integration patterns

DigitalStack Execute
Canonical work-item source and explicit field-update target.
Claude / ChatGPT / IDE clients
Create proposal runs, review generated drafts/artifacts, and prepare apply packages through MCP.
GitHub / GitLab / Bitbucket
Future authorized repository context for code inspection and implementation planning.No native DigitalStack connector currently exists for this system.

Related guides

REST API reference

Explore

GraphQL overview

Explore

MCP overview

Explore

Authentication & scopes

Explore

Webhooks overview

Explore