Skip to content
Spark.
AssistantEngineeringManagement

Turn dev-sync talk into a ticket and its first prompt

A dev sync's notes become a proper Jira ticket plus a ready-to-paste dev prompt for each development action point; unknowns are flagged, not guessed, and the engineer reviews before creating.

Updated

Before you start

What you need
Notes from the sync. The ticket fields ship with the skill, so there is nothing else to supply.
Connector (MCP)
Recommended. It reads the notes your notetaker already produced, so you do not copy them out after every sync.
Without a connector
Paste the notes into the chat. It writes nothing to your tracker either way.

A connector, often called MCP, lets an assistant read your tools directly instead of you pasting. Set it up once, then it reads those tools on its own. How that is done differs per assistant, so check its own documentation.

How to try it

  1. Download the skill and unzip it. Inside are the instruction, the ticket and dev-prompt templates, and a page on loading it.
  2. If your assistant reads skills, copy the dev-tickets folder into the place it reads them from. If it does not, use Copy as text instead: that is the same instruction with both templates already inlined.
  3. Compare its tickets with the ones you wrote, and read the starter prompt as the developer who would receive it.
  4. Check that discussion stayed out, and that anything unsettled came back marked [verify: owner] rather than guessed.
  5. Use it after the next sync. Nothing reaches your tracker until you put it there.
Download skill

Download to install it once. Copy to paste it into a chat.