Redmine Agent-Ready Tickets

Convert issue history and product intent into small, evidence-backed implementation contracts. Preserve why the work exists while removing ambiguity about what must be delivered and how completion will be verified.

Load the supporting material

• Read references/ticket-contract.md before drafting or rewriting any ticket.
• Read references/restructuring-patterns.md when a backlog contains duplicates, research mixed with implementation, more than one independently releasable outcome, or unclear parent/child relationships.
• Run scripts/validate_ticket.py against each final draft when the ticket body is available as a file.

Workflow

1. Establish scope and authority

Identify the Redmine project, requested ticket set, target language, and whether the user asked for an audit, drafts, or live updates. Treat reading and drafting separately from changing Redmine.

Prefer a purpose-built Redmine connector, API, or CLI. Use browser interaction only when no suitable integration exists or the user explicitly requests it. Follow the active tool's confirmation policy before saving live changes.

2. Capture the source of truth