orchestra-prd

Included with Lifetime

$97 forever

Define the what and why for a piece of work — objective, success criteria, materials table, and context. The foundational Score document before any spec is written.

General

What this skill does


# Write PRD

Define the what and why for a piece of work. The PRD is the foundational Score document — it must exist and be approved before any spec is written.

## Prerequisites

- `.orchestra/roadmap.md` must exist
- Read the roadmap and any active milestone PRD for context — but a milestone gap is not required to write a PRD

## Steps

### 1. Establish Context

- Read `.orchestra/roadmap.md` to understand the project vision
- Identify which milestone this PRD serves
- Read the milestone PRD to understand the objective and surrounding deliverables
- Read any relevant ADRs in `.orchestra/adr/`

### 2. Gather Requirements

Ask the user:
- **What is the objective?** What does "done" look like?
- **Why does this matter?** How does it serve the milestone?
- **What are the deliverables?** Files, documents, features, or artifacts
- **What are the constraints?** Technical, timeline, dependencies
- **What are the success criteria?** How do we know it worked?

If the user provides $ARGUMENTS with a description, use that as the starting point and ask only for gaps.

### 3. Generate the PRD

Generate the PRD with this structure:

- **Title**: Clear, specific name
- **Objective**: 1-2 sentences — what "done" looks like
- **Success Criteria**: 3-5 testable checkboxes
- **Context**: Why this matters, what milestone it serves, what problem it solves
- **Materials table**: Each deliverable with location and "Not Started" status
- **References**: Link to milestone PRD, relevant ADRs, external docs
- **Notes**: Constraints, open questions, dependencies

### 4. Determine Work Item ID

- If a ticket ID exists from an issue tracker, use `{ticket-id}-{short-name}`
- If no ticket yet, use a descriptive slug: `{short-name}`
- The user can rename the folder later when a ticket is assigned

### 5. Write the File

Save to: `.orchestra/work/{id}-{name}/prd.md`

Include YAML frontmatter at the top of the file:

```yaml
---
ticket: {ticket-id or slug — matches the work item folder name}
status: draft
created_on: {today's date in YYYY-MM-DD format}
---
```

Status vocabulary for PRDs: `draft` → `approved` → `complete`

### 6. Update the Milestone

If an active milestone PRD exists in `.orchestra/roadmap.md`:
- Add or update the row in that milestone's materials table:

```markdown
| {PRD title} | .orchestra/work/{id}-{name}/prd.md | Not Started |
```

If no active milestone exists, skip this step and note it in the report — the work item can be assigned to a milestone later.

### 7. Present for Approval

Show the user the complete PRD. Ask:
- Does the objective capture what you want?
- Are the success criteria testable and complete?
- Is anything missing from the materials table?
- Should we proceed to write a spec?

## Quality Checks

- [ ] Objective is specific — not "improve the thing" but "add X that does Y so Z"
- [ ] Success criteria are testable — each one can be checked as done/not done
- [ ] Materials table lists concrete deliverables with file paths
- [ ] Context explains why this work matters — and traces to a milestone if one exists
- [ ] No open questions left unaddressed (flag them if unresolved)

Files: 3

Size: 6.7 KB

Complexity: 17/100

Category: General

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

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