Turning a planning document into well-formed tickets takes a product manager most of an afternoon. An Orkeste agent reads the planning page in Confluence or Notion, splits it into stories with acceptance criteria and creates the issues in Jira once the PM approves them.
The problem
Specs are written in one place and tickets in another. Copying them across loses detail, and acceptance criteria are written in a hurry or not at all.
How the workflow runs
Runs: When you start it with a planning page.
Read the plan: The agent reads the planning page in Confluence or Notion, or the text you paste.
Split into stories: It breaks the plan into stories small enough for one person.
Write acceptance criteria: Each story gets a clear title, a description and acceptance criteria.
Approve: Each issue waits in Validations: the PM edits, approves or drops it.
Create in Jira: Approved issues are created in the project you name, with a reference to the plan.
No issue is created in Jira until the PM approves it.
Who does what
Story writer: Turns a plan into issues with acceptance criteria.
Product manager (human): Approves every issue before it is created.
What this workflow does not do
Creates issues; it does not add them to a sprint, assign them or set story points.
Reads plans in Confluence or Notion; the content of Google Docs is not read.
Does not edit existing issues, only comments on them.