Capabilities
Sprints & Planning
Read sprint planning context, readiness, and proposal-only next moves without letting planning projections become authoritative execution placement.
Interfaces
Public REST exposes planning context/readiness and deterministic suggestion generation. Suggestions create reviewable intents only; they do not move work.
MCP can read sprint reports, inspect sprint-planning readiness, and generate confirmed proposal-only planning moves.
GraphQL exposes sprintPlanning(projectId) and generateSprintPlanningSuggestions(input) through the same public service layer and sprints:read scope.
Suggestion-generation commands emit sprint_planning.suggestions_generated through the durable signed webhook outbox.
Required scopes
sprints:readAPI key scoperequiredagent:readAPI key scoperequiredExamples
Get sprint planning context — view in REST API reference
curl -X GET "https://www.digitalstack360.com/api/v1/projects/proj_abc123/sprint-planning" \
-H "Authorization: Bearer $DS_API_KEY"Generate sprint planning suggestions — view in REST API reference
curl -X POST "https://www.digitalstack360.com/api/v1/projects/proj_abc123/sprint-planning/suggestions" \
-H "Authorization: Bearer $DS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"confirm":true}'GraphQL examples
sprints:readFetch readiness and the underlying read-only planning context.
query SprintPlanning($projectId: ID!) {
sprintPlanning(projectId: $projectId) {
projectId
generatedAt
readiness {
score
verdict
criteria {
id
status
severity
reason
}
}
context
}
}sprints:readReturn citation-gated proposed intents and emit a webhook fact; no execution substrate is mutated.
mutation SuggestSprintPlanning($input: GenerateSprintPlanningSuggestionsInput!) {
generateSprintPlanningSuggestions(input: $input) {
ok
result {
actionKind
observations
webhookEventType
readiness { score verdict }
intents
}
errors { code message }
}
}Webhook emits
sprint_planning.suggestions_generatedAvailableA Sprints & Planning suggestion batch was generated for review. This is proposal-only and does not apply a plan.
Resource: sprint_planning
project_idaction_kindreadiness_scorereadiness_verdictintent_countobservation_countcomputed_atAll 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
- • Sprint-planning context composition and readiness scoring
- • Proposal-only planning intents and citation gates
- • Durable facts that a planning-suggestion batch was generated
Source systems own
- • Provider board iteration identity and source issue fields until mapped into DigitalStack
- • Human commitment decisions and actual execution placement
Typical integration patterns
JiraAzure DevOps / LinearClaude / ChatGPT / IDE clients