presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/phase-transition_3to4.prompt.md

phase-transition_3to4 is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (603 once invoked), scanned A, original, MIT.

A transition command for moving from architecture design into detailed design, while keeping design documents connected to GitHub Issues. It describes how requirements, architecture decisions, component designs, code, and tests should reference one another.

In plain words
What is it for?
Use it to update architecture issues, create supporting design documents, record component details, and maintain links between requirements and planned tests.
Why use it?
It reduces traceability gaps where a detailed design cannot be tied back to the requirement or architecture decision that prompted it.

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/phase-transition_3to4.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 phase-transition_3to4

README.md
[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4)
Your own site
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4/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 phase-transition_3to4

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4.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 603 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.00603
Opus 5 $0.00000 $0.00302
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

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

Security

Grade A, and why

phase-transition_3to4 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/phase-transition_3to4.prompt.md · 51 lines

What it actually says

Phase 04: Detailed Design - Standards-Compliant Transition

GitHub Issues Workflow: Update architecture component issues (ARC-C) with detailed design specifications. Add design comments to architecture issues or create supplementary design documentation that references issues. Maintain traceability via issue references: #REQ → #ARC-C → code implementation → #TEST.

Design Documentation: You may create supplementary design markdown files in 04-design/components/, but they MUST reference the canonical GitHub Issues using #N syntax:

# Component Design: User Authentication

**Architecture Issue**: #45 (ARC-C-AUTH-001: Authentication Service)
**Requirements**: #23 (REQ-F-AUTH-001), #24 (REQ-NF-SECU-002)

## Component Structure
[Detailed design content here...]

Context: I have completed Phase 03 (Architecture Design) following ISO/IEC/IEEE 42010:2011 standards and am ready to transition to Phase 04 (Detailed Design) following IEEE 1016-2009 standards.

Completed Architecture Artifacts:

  • Architecture specification with multiple viewpoints (Context, Logical, Deployment)
  • Architecture Decision Records (ADRs) documenting key decisions
  • All ADRs have rationale and link to requirements
  • Quality attribute scenarios (Performance, Availability, Security)
  • Architecture evaluation completed
  • All architecture components identified with ARC-C-* IDs
  • Traceability matrix linking requirements (REQ-) to architecture components (ARC-C-) and ADRs

Phase 04 Objectives (per IEEE 1016-2009):

  1. Transform architecture components into detailed component designs
  2. Specify interfaces, data structures, and algorithms
  3. Create component-level design descriptions
  4. Maintain traceability: ARC-C-* → DES-C-* → implementation units
  5. Apply XP Simple Design principles (YAGNI, minimal complexity)

Standards to Apply:

  • IEEE 1016-2009: Software Design Descriptions format
  • ISO/IEC/IEEE 12207:2017: Design Definition process
  • XP Practices: Simple Design, Refactoring readiness, Test-first design

Specific Request (enforce traceability & unique IDs): Please guide me through Phase 04 detailed design activities:

  1. Review my architecture artifacts for design readiness
  2. Help create component design specifications using IEEE 1016 format
  3. Define interfaces and data models with proper traceability
  4. Prepare test-driven design approach for Phase 05 implementation
  5. Ensure design decisions support XP practices (especially TDD and refactoring)

Questions for Clarification (Answer before generating design specs):

  • Should I prioritize certain architecture components for detailed design first?
  • Are there specific performance or complexity constraints I should consider?
  • What level of design detail is appropriate for the implementation approach planned?
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 · 51 lines · 0 tokens per session scan A 3c7ddb159e27

Subscribe to this mod's changes

phase-transition_3to4 is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 603 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.