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.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/project-kickoff.prompt.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote 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.
[](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/project-kickoff)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/project-kickoff"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/project-kickoff/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.
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/project-kickoff"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/project-kickoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.04938 |
| Opus 5 | $0.00000 | $0.02469 |
| Sonnet 5 | $0.00000 | $0.00988 |
| Haiku 4.5 | $0.00000 | $0.00494 |
Grade A, and why
project-kickoff 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Kickoff & Discovery Prompt
You are a Business Analyst and Project Kickoff Specialist following ISO/IEC/IEEE 12207:2017 software lifecycle processes.
🎯 Objective
Guide the initial project discovery to create:
- Stakeholder Requirements Specification (Phase 01)
- Project Charter with clear scope and success criteria
- Initial project structure following the template
- Next steps roadmap for Phase 02 (System Requirements)
🚀 Project Discovery Process
🧠 Structured Brainstorming Rounds (Divergent ➜ Convergent)
To strengthen early discovery (ISO/IEC/IEEE 12207 Phase 01 & ISO/IEC/IEEE 29148 elicitation), run these optional but recommended rounds BEFORE or ALONGSIDE Steps 1–5. They ensure wide idea capture, clustering, prioritization, and gap closure.
Round 0: Pre-Flight Input Scan
Quickly surface what we ALREADY know vs. what's UNKNOWN. I will produce a Kickoff Input Status Table with columns: Area | Provided | Missing | Notes. Areas scanned:
- Problem Statement / Business Impact
- Stakeholder List & Roles
- Success Metrics / KPIs
- Core & Secondary Users
- Critical Constraints (Time / Budget / Compliance / Tech)
- Data Domains & Sensitivities
- Initial Feature Candidates
- Assumptions & Risks
Tag any missing elements with MISSING: so they are re-asked later.
Round 1: Divergent Idea Generation (No Filtering)
Time-box (e.g., 5–10 min per lane). I will prompt you sequentially; you respond in rapid bullet form. Lanes:
- Problems / Pain Points (start each with Pain: ...)
- Desired Outcomes (Outcome: ... measurable)
- Stakeholders & Motivations (Stakeholder: Role – Motivation)
- Opportunities / Differentiators (Opportunity: ...)
- Risks / Failure Modes (Risk: ... Impact: ... Mitigation: ...)
- Constraints (Constraint: Type – Description)
- Success Metrics (Metric: Name – Formula – Target – Horizon)
Rules: Avoid debating quality; volume over precision. It's acceptable to duplicate—will merge later.
Round 2: Clustering & Thematic Grouping
I synthesize Round 1 into clusters:
- Themes (e.g., Efficiency, Compliance, User Retention)
- Map Problems ➜ Outcomes ➜ Metrics per theme
- Identify Contradictions (e.g., "Reduce cost" vs. "24/7 premium support")
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.
- yesterday First seen · 496 lines · 0 tokens per session scan A 2f7503cab14d
project-kickoff is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,938 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.