Plan Tickets

Normalize inputs, classify each work item, apply title conventions, draft tickets in a standard structure, then either return markdown drafts or create issues in the issue tracker after explicit approval.

See EXAMPLES.md for a complete plan → ticket draft example.

Workflow

1. Normalize the initiative

Extract planning inputs:

• initiative/theme
• project/board
• whether the request is draft-only or create-in-tracker
• default sprint or backlog bucket
• constraints on issue types, prefixes, epic, labels, components, status, or sprint

If the user already has a plan, do not re-plan unless there is a material gap.

2. Classify each ticket before drafting it

Assign these core planning attributes to each ticket:

Additional attributes to apply when relevant: coordination_need (single-team | multi-team), external_dependency (yes | no), urgency (normal | priority).

Backend/API enablers generally come before dependent web/mobile tickets.

3. Apply title conventions

Use these prefixes:

• BE | for backend
• FE | for web / frontend
• Mobile | for mobile

When writing the ticket title, leave a space after the |.

Do not add those prefixes to tickets that are not owned by those areas unless the user explicitly wants that.

4. Draft tickets in the standard structure

Use this section order:

Keep the main sections business-facing.

5. Output: drafts or create in the issue tracker

Draft-only:

• Return markdown tickets following the five-section structure (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes) with the appropriate area prefix in the title.
• Keep titles, issue types, and dependencies explicit.
• Include brief sequencing notes when helpful.
• See EXAMPLES.md for a full plan → ticket draft with classification applied.

Create in issue tracker:

• Verify the target project/board details first.
• Confirm required fields: project, issue type, sprint, status behavior, epic, labels, components.
• Create issues only after the plan is considered approved enough.
• Use whatever integration the user has (API, MCP, UI); do not assume credentials in the repo.
• Validate one issue before bulk-creating if the sprint field or workflow behavior is uncertain.
• After creation, report: created issue keys, confirmed status, confirmed sprint/bucket, and any assumptions used.

Example field shape for MCP/API creation:

{
  "project": "<project-key>",
  "issuetype": "Story",
  "summary": "BE | Enable payment webhook processing",
  "description": "<full ticket body>",
  "labels": ["payments", "backend"],
  "components": ["payments-service"],
  "sprint": { "id": "<sprint-id>" },
  "epic": "<epic-key>"
}

Omit fields the project does not require. Confirm actual field names from the tracker's create-metadata endpoint before issuing the call. Do not set status on create — use the project's default initial status.

Sprint Placement Heuristics

Defaults unless the user overrides:

• foundation and api tickets → placed before all dependent client tickets
• client tickets → blocked until the API surface they depend on is stable
• external confirmation tickets → excluded from active build sprints
• follow-up tickets → ready-to-refine or later until their enabling work is complete
• Named future sprints (e.g. Ready to Refine) → treat as a planning bucket, not an execution commitment

Integration

Assets

• assets/ticket-samples/sample_issue.md