orchestra-ticket

Included with Lifetime

$97 forever

Capture a work ticket as the starting point for the orchestra loop — read a brief, scaffold the work item folder, and set up for PRD and spec.

General

What this skill does


# Ticket

Capture a work ticket and scaffold the orchestra work item. The ticket is the contract — the starting point for the loop.

## Flow

```
/orchestra-ticket → /orchestra-plan (PRD → Spec → Gherkin) → /orchestra-implement → /orchestra-review → /orchestra-merge
```

## Steps

### 1. Read the Brief

From $ARGUMENTS, determine the source:

- **Issue tracker ID or URL** — fetch the ticket if an integration is installed. Use the task ID to retrieve title, description, and acceptance criteria.
- **Text description** — the user is providing the brief directly

Extract: title, objective, any acceptance criteria, priority, context.

### 2. Check for Existing Work Item

Derive the slug: `{ticket-id}-{short-name}` (if from an issue tracker) or `{short-name}` (if from a text brief).

Check if `.orchestra/work/{slug}/` already exists.

**If it exists:** show what's there (ticket.md, prd.md, spec.md) and stop. Don't overwrite.

### 3. Scaffold the Work Item

Create the folder and write the ticket file:

```
.orchestra/work/{slug}/
└── ticket.md
```

**ticket.md format:**

```markdown
# {Title}

**Source:** {issue tracker link or "user brief"}
**Priority:** {if known}
**Date:** {today}

## Brief

{The ticket description — what was asked for, in the requestor's words}

## Acceptance Criteria

- [ ] {From the ticket, or "To be defined in PRD"}

## Notes

{Any constraints, context, or references from the original ticket}
```

### 4. Update the Milestone

If an active milestone exists in `.orchestra/roadmap.md`:
- Add a row to the milestone PRD's materials table pointing to the new work item
- If no active milestone, note this in the output — the user can assign it later

### 5. Report

```
## Ticket Captured

- **Title:** {title}
- **Slug:** {slug}
- **Path:** .orchestra/work/{slug}/ticket.md
- **Milestone:** {milestone name or "unassigned"}

### Next Steps
1. Run `orchestra-prd {slug}` to expand the brief into a full PRD
2. Run `orchestra-spec {slug}` to plan execution
3. Implement and log with `orchestra-devlog`
```

## Rules

- Never overwrite an existing work item — check first, always
- The ticket.md preserves the original brief — don't rewrite or improve it
- Every ticket gets a PRD and spec downstream — keep the folder ready for both
- If the brief is vague, capture it as-is — the PRD step is where clarity happens

Files: 3

Size: 5.3 KB

Complexity: 16/100

Category: General

Source: https://github.com/mpazaryna/agentic-factory/tree/main/skills/orchestra-ticket

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts