chat
/chat
Starts the ticket workflow from a request typed in chat, without a Jira or Linear ticket. Turns "fix this bug" or "add this feature" into a local ticket with testable acceptance criteria and a CHAT-<n> key, then runs the normal track. Use when someone asks in chat to fix, build, add or change something and gives no ticket key.
- Author
- aniketshukla1 ↗
- Repository
- sdlc-kit ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Starts the ticket workflow from a request typed in chat, without a Jira or Linear ticket. Turns "fix this bug" or "add this feature" into a local ticket with testable acceptance criteria and a CHAT-<n> key, then runs the normal track. Use when someone asks in chat to fix, build, add or change something and gives no ticket key.
Triggers from the description
Original author description
Starts the ticket workflow from a request typed in chat, without a Jira or Linear ticket. Turns "fix this bug" or "add this feature" into a local ticket with testable acceptance criteria and a CHAT-<n> key, then runs the normal track. Use when someone asks in chat to fix, build, add or change something and gives no ticket key.
How it works
- Steps
- Done when
SKILL.md preview
---
name: chat
description: Starts the ticket workflow from a request typed in chat, without a Jira or Linear ticket. Turns "fix this bug" or "add this feature" into a local ticket with testable acceptance criteria and a CHAT-<n> key, then runs the normal track. Use when someone asks in chat to fix, build, add or change something and gives no ticket key.
---
# Start from chat (no ticket)
A request typed in chat becomes a local ticket, so the same tracks, tests first and checks apply. A chat ticket
has no tracker: what the workflow would post to a ticket, you say in chat and log in PROGRESS.md.
## Steps
1. Type: Bug (something is broken), Feature (new or changed behaviour) or Task (no behaviour change: a refactor,
an upgrade). Unclear → ask.
2. Draft the ticket with the template for its type, from `.cursor/skills/jira-create/`: Bug → `bug-template.md`,
Feature → `enhancement-template.md`, Task → `task-template.md`. Keep every heading.
- At the top: `Type: <Bug|Feature|Task>`, then the request word for word on a `Request:` line.
- The request says nothing about a section: write `None`, or add a line under Open Questions. Never invent
steps, error text, numbers, names or root causes.
- Acceptance criteria: numbered, each one a check a test can make (Given / When / Then fits most).
- Leave out Sub-tasks. More than one mergeable part → ask the human to split it into separate requests.
3. Missing parts (Bug: steps to reproduce, actual and expected result; Feature and Task: acceptance criteria):
ask for them in ONE message (max 5 questions), each with your best guess so the human can answer "yes".
4. Show the draft. Then write exactly: `Reply "start" or "changes: <feedback>".` STOP.
5. On `start`, pick the key: `n` = 1 + the highest number after `CHAT-` in `.agent/work/` and in
`git branch -a --list '*CHAT-*'` (after `git fetch -q origin`), or 1 if there's none. The key is `CHAT-<n>`.
6. Save the draft as `.agent/work/CHAT-<n>/TICKET.md`. Tell the human the key: `Continue CHAT-<n>` picks it up
in a new chat, like any ticket.
7. Start the track for `CHAT-<n>`: Bug → /quick-fix. Feature or Task → /ticket-intake (the full track).
## Done when
- [ ] The human typed `start`; TICKET.md has the request word for word and testable acceptance criteria
- [ ] The track's first skill runs for `CHAT-<n>`
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · aniketshukla1/sdlc-kit | 90 | MIT |
| promptctl/laws | 100 | MIT |
| vercel-labs/json-render | 95 | Apache-2.0 |
| zerogpu/zerogpu-router | 87 | MIT |
| zerogpu/zerogpu-router | 87 | MIT |
| aws-samples/sample-aws-devops-agent-claude-plugin | 84 | MIT |
Database snapshot: 13.11.2026 · package version 0c933e935746 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ticket-intake
Phase 1 of the full track (Story, New Feature, Improvement, Enhancement, Task). Fetches the ticket through the tracker's MCP server (Jira or Linear) and turns it into testable requirements and open questions. Use when starting a full-track ticket like PROJ-123. - 100story-author
Turn a raw feature idea, improvement, or bug description into a structured user story with testable acceptance criteria, persisted as a local markdown file. Invoke when the user wants to create, draft, or refine a story, ticket, requirement, or acceptance criteria — trigger… - 90ticket-qa
QA for a ticket (Jira or Linear). Turns its acceptance criteria into a pass/fail plan (golden path, edge cases, errors, compatibility), runs what it can locally, gives the human exact steps for the rest, records evidence, and posts the result to the ticket after the human types… - 100jira-bug-ticket
Create a Jira bug ticket. Use when the user asks to file, log, report, or create a bug or defect in Jira ("create a bug ticket", "log a bug", "report a bug", "open a ticket for this bug"). - 100jira-ticket-writer
Writes ready-to-build Jira stories with user-story summaries, Given/When/Then acceptance criteria, subtasks, and story-point guidance, checked against INVEST and a Definition of Ready. Use when someone asks "write a Jira ticket for this", "turn these meeting notes into a story",… - 100linear-requirement
Draft and file a Sokosumi Linear requirement issue (## Requirement) after user approval. Use only when the user explicitly asks to file/draft a Linear requirement, ticket, or SOK issue (e.g. "file this as a Linear issue", "draft a requirement", "create a SOK ticket",…