presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/user-story-expansion.prompt.md

user-story-expansion is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (4,176 once invoked), scanned A, original, MIT.

A planning prompt that expands large features into detailed user stories for Agile teams. Agile is a way of organising software work in small, reviewable pieces; it also adds acceptance checks in Given-When-Then form.

In plain words
What is it for?
Use it to break epics into implementation-ready stories, write acceptance criteria, and connect stories to stakeholder requirements.
Why use it?
It turns vague feature requests into smaller work that developers can estimate, build, and verify. It also covers user roles, normal cases, errors, edge cases, business rules, and validation.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells GitHub Copilot how to work on presonus-studiolive-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything presonus-studiolive-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/user-story-expansion.prompt.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for user-story-expansion

README.md
[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/user-story-expansion/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/user-story-expansion)
Your own site
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/user-story-expansion"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/user-story-expansion/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for user-story-expansion

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/user-story-expansion"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/user-story-expansion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,176 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04176
Opus 5 $0.00000 $0.02088
Sonnet 5 $0.00000 $0.00835
Haiku 4.5 $0.00000 $0.00418

Measured 3d ago against content hash fa350704307d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

user-story-expansion scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/user-story-expansion.prompt.md · 568 lines

How it starts

The opening of the file, as written. The whole thing — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Story Expansion Prompt

You are a Product Owner and Business Analyst following Agile/Scrum best practices and ISO/IEC/IEEE 29148:2018.

🎯 Objective

Transform epics and high-level features into detailed, implementable user stories with:

  1. INVEST criteria compliance (Independent, Negotiable, Valuable, Estimable, Small, Testable)
  2. Complete acceptance criteria in Given-When-Then format
  3. Traceability to stakeholder requirements
  4. Implementation-ready details for development teams

📋 User Story Expansion Process

Step 1: Epic Analysis

Input: Epic or high-level feature description

Questions to Ask:

  • Who are the different user types that need this feature?
  • What are the different ways this feature could be used?
  • What are the different scenarios (happy path, error paths, edge cases)?
  • What business rules apply?
  • What validation is needed?

Step 2: Story Decomposition

Break down epic into stories using these patterns:

By User Role
Epic: "Users can manage their profile"
↓
- As a new user, I want to create my profile
- As an existing user, I want to update my profile  
- As an admin, I want to view user profiles
- As a user, I want to delete my profile
By Workflow Steps
Epic: "Users can complete checkout process"
↓
- As a customer, I want to review my cart
- As a customer, I want to enter shipping info
- As a customer, I want to select payment method
- As a customer, I want to confirm my order
- As a customer, I want to receive order confirmation
By Business Rules
Epic: "System processes payments"
↓
- As a customer, I want to pay with credit card
- As a customer, I want to pay with PayPal
- As a customer, I want to apply discount codes
- As a customer, I want to handle payment failures
- As a system, I want to verify payment before fulfillment
By Data Operations (CRUD)
Epic: "Manage product catalog"
↓
- As an admin, I want to add new products
- As an admin, I want to update product info
- As a customer, I want to view product details
- As an admin, I want to remove discontinued products

Read the full file on GitHub · 568 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 568 lines · 0 tokens per session scan A fa350704307d

Subscribe to this mod's changes

user-story-expansion is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,176 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.