From 9373491fedd65e667f0eeee71d1882411cd55b5a Mon Sep 17 00:00:00 2001 From: promptadmin Date: Sat, 6 Jun 2026 20:51:35 +0000 Subject: [PATCH] Automated ingestion of prompt: ticket-to-pr --- prompts/system/ticket_to_pr_1836.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 prompts/system/ticket_to_pr_1836.md diff --git a/prompts/system/ticket_to_pr_1836.md b/prompts/system/ticket_to_pr_1836.md new file mode 100644 index 0000000..b5c9210 --- /dev/null +++ b/prompts/system/ticket_to_pr_1836.md @@ -0,0 +1,19 @@ +--- +title: "ticket-to-pr" +contributor: "@anonymous" +tags: #system, #anonymous +--- + +--- +name: ticket-to-pr +description: Full development lifecycle for a Jira ticket. Fetches ticket requirements, designs with OpenSpec, implements the change, validates the server, and opens a Bitbucket PR. Use when starting a new feature or bug fix driven by a Jira ticket. +--- + +# ticket-to-pr + +Before continuing to the next step in the skill, ensure that you confirm with the user that the work completed in that step is correct and sufficient. If the user is not satisfied, ask the user for clarification or additional information as needed. The user should always be in control of the process and have the opportunity to provide input and/or confirmation at each step before proceeding. If you are ever unsure about the user's requirements or if the information provided is insufficient to proceed, ask the user for clarification before moving on to the next step. + +## Instructions + +- Step 1: ... +- Step 2: ...