A repeatable, high-discipline workflow for Cursor (and similar IDE agents): fetch issue → branch → implement → tests → Confirm → commit → Confirm → PR → ask before chat.
Live site: https://smg99.github.io/ticket-flow/
Companion SDLC method: AI-Assisted SDLC Playbook — stage prompts from vague requirements through release. This repo sequences how an IDE agent runs once a real ticket exists (Develop one story).
Ticket Flow is a thin orchestration layer, not a product.
User phrase → rule loads skill → scripts + product repos → Confirm → commit/PR → ask before chat
Ad-hoc chat ("plan then build ticket X") often burns retries: wrong branch, forgotten tests, premature commit, or Slack spam. A Ticket Flow skill front-loads the path once.
ticket-flow/
├── index.html # Public GitHub Pages site
├── AGENTS.md # Agent entrypoint (gates, scripts, skills)
├── skills/ticket-flow/SKILL.md # Canonical portable skill
├── assets/ # Site CSS, JS, OG image
├── README.md
├── LICENSE # MIT
├── .cursor/
│ ├── skills/ticket-flow/SKILL.md # Symlink/copy → skills/
│ └── rules/
│ ├── ticket-flow.mdc
│ └── ticket-handoff.mdc
├── docs/
│ ├── ticket-flow-agent-guide.md
│ ├── progress-template.md
│ ├── execution-evidence.md
│ ├── CONTRIBUTING.md
│ └── assets/
├── scripts/ # Thin CLI wrappers (fail loud until configured)
└── tests/run.sh # Wrapper regression tests (no credentials)
- Visit the live guide (or open
index.htmllocally). - Copy
skills/ticket-flow/,.cursor/rules/*.mdc, and the Cursor skill adapter (.cursor/skills/) into your product repo (or multi-root this repo). SeeAGENTS.md. - Configure
scripts/for your issue tracker and chat — unconfigured scripts error; they do not invent data. - Copy
docs/progress-template.md→.local/progress.md(gitignored). After PR open, status isawaiting_review—notdone. - In chat:
work on ticket PROJ-123. - Optional:
./tests/run.shto verify wrapper failure paths locally.
- Site: index.html · start/ · guides/
- AI context: llm.txt · llms.txt · llms-full.txt
- Crawlers: robots.txt · sitemap.xml
GitHub Pages publishes the repository root from main. .nojekyll disables Jekyll processing. No build step, framework, or backend.

