{
"schema_version": 3,
"name": "tracked-release",
"concurrency": 3,
"goal": {
"text": "Deliver the tracked release safely across its target projects"
},
"tasks": [
{
"id": "design",
"persona": "planner",
"task": "## What\nDesign the release and record its API and rollout contract in docs/design.md.\n\n## Why\nGive implementers and approvers one stable contract so the release can proceed without incompatible assumptions.\n\n## Acceptance criteria\n- The API and rollout contract is complete.\n- The design is verified against the current project."
},
{
"id": "design-approval",
"kind": "human",
"task": "Approve the API and rollout contract in docs/design.md.",
"deps": ["design"]
},
{
"id": "service",
"repo": "nickderobertis/some-service",
"repo_type": "team",
"deps": ["design-approval"],
"title": "feat: implement approved release",
"executor": "local",
"steps": [
{
"id": "implement",
"persona": "engineer",
"task": "## What\nImplement the approved API and rollout behaviour and write the tests that prove it.\n\n## Why\nDeliver the approved release behaviour to service users without breaking the agreed contract, with the implementation fully proven in its own dispatch.\n\n## Acceptance criteria\n- The approved API and rollout behaviour are implemented.\n- Realistic request tests prove the happy path and a failure or recovery path, without opening coverage gaps.\n- Each new test is observed failing for the intended reason before it passes.\n- The repository's own full gate is green."
},
{
"id": "staging-approval",
"kind": "human",
"task": "Exercise the staged service and approve continuation on this branch.",
"deps": ["implement"]
}
]
},
{
"id": "docs",
"repo": "nickderobertis/some-docs",
"repo_type": "team",
"persona": "docs-writer",
"title": "docs: document the approved API and rollout",
"body": "## What\nDocuments the approved API and its rollout steps.\n\n## Why\nUsers adopting the release need accurate operating instructions to follow.",
"agent_graph": "./graphs/node-scope.yaml",
"task": "## What\nDocument the approved API and rollout.\n\n## Why\nEnable users to adopt the release confidently with accurate operating instructions.\n\n## Acceptance criteria\n- The approved API and rollout are documented.\n- Every command is verified against the implementation.",
"deps": ["design-approval"]
},
{
"id": "readiness-handoff",
"task": "## What\nRecord that the readiness handoff expects no repository change.\n\n## Why\nMake the no-change boundary explicit so the release does not spend provider time on an unnecessary dispatch.\n\n## Acceptance criteria\n- The handoff records the no-change expectation.",
"expects_no_diff": true,
"deps": ["service", "docs"]
},
{
"id": "release-approval",
"kind": "human",
"task": "Approve publication after reviewing the service and documentation results.",
"deps": ["readiness-handoff"]
}
]
}