AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Repeatable IDE agent checklist from ticket ID to PR: Confirm gates, path-scoped staging, tests required, ask before chat.
Translation pending
Developer toolsHTML · JavaScriptGitHub @smg99OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
A repeatable, high-discipline workflow pattern for Cursor agents: fetches issues, branches, implements, adds tests, runs human confirmation gates, commits, PRs, and notifies chat.
Taken from the repository README
Loading the full README.
Read the full README ↗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
├── assets/ # Site CSS, JS, OG image
├── README.md
├── LICENSE # MIT
├── .cursor/
│ ├── skills/ticket-flow/SKILL.md
│ └── rules/
│ ├── ticket-flow.mdc
│ └── ticket-handoff.mdc
├── docs/
│ ├── ticket-flow-agent-guide.md
│ ├── progress-template.md
│ ├── CONTRIBUTING.md
│ └── assets/
└── scripts/ # Thin CLI wrappers (fail loud until configured)
index.html locally)..cursor/rules/*.mdc and .cursor/skills/ into your product repo (or multi-root this repo).scripts/ for your issue tracker and chat — unconfigured scripts error; they do not invent data.docs/progress-template.md → .local/progress.md (gitignored).work on ticket PROJ-123.GitHub Pages publishes the repository root from main. .nojekyll disables Jekyll processing. No build step, framework, or backend.