Quick start
Thirty minutes to wire Ticket Flow into a team. Ticket Flow is a thin IDE agent checklist from a real ticket ID to a pull request with human Confirm gates—not a hosted platform.
1. Copy skill and rules
Copy .cursor/skills/ticket-flow/ and .cursor/rules/*.mdc into your product repo’s .cursor/ directory, or open this repository as a multi-root workspace.
- Skill — the checklist the agent follows.
- ticket-flow.mdc — routes trigger phrases to the skill.
- ticket-handoff.mdc — Impact Area + tests on handoff/PR.
2. Configure scripts
Edit wrappers under scripts/. Unconfigured scripts exit with an error—they never invent ticket text or claim a chat send succeeded.
issue-get.sh→ Jira / Linear /gh issue viewgit-branch.sh,git-commit.sh,git-push.sh,git-pr.shnotify-chat.sh→ webhook or chat CLI (channel required)
3. Progress board
Copy docs/progress-template.md to .local/progress.md (gitignored) for morning multi-ticket queues.
4. Run a ticket
In Cursor chat, say:
work on ticket PROJ-123
Also works: fix bug PROJ-123 / process morning queue. Expect Confirm before commit and before PR. Silence is not Confirm.
Vague requirements first? Use the playbook review-markdown, then return for Develop one story with Ticket Flow.