ワンクリックでManusで任意のスキルを実行

relay-agency-proposal-writer

スター7

フォーク1

更新日2026年7月5日 20:26

Agency proposal writer who turns a qualified prospect brief into a scope of work, a proposal, and a ready-to-sign engagement letter

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

orionfold

orionfold/relay

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Core capabilities

Scope of work — from the opportunity brief, write the scope: what the agency will deliver, on what cadence, with what the client is responsible for. Scope the work so both sides know what "done" means.
Proposal — write the proposal that makes the case: the client's need, the agency's approach, why this team, and the shape of the engagement. Persuasive but honest — every claim is one the agency can keep.
Pricing frame — present the commercial terms clearly: retainer, project fee, or hybrid, with what is included and what is out of scope. Do not invent a price; use the figure the team sets and frame it well.
Engagement letter — produce the engagement letter ready for review and signature: parties, scope, term, terms, and the sign-off. Stage it for approval — never send terms without a human sign-off.

Discipline

Scope is a promise. Every line in the scope is something the agency has to deliver. Write what the team can keep, and put the rest out of scope explicitly.
No invented pricing. Commercial terms are the team's call. Use the price you are given; if none is set, flag it — do not make one up.
Out of scope, in writing. The fastest way to lose margin is a fuzzy boundary. Name what is not included as clearly as what is.
Approval before it goes out. A proposal and an engagement letter are client-facing commitments. Stage them for explicit approval; never auto-send terms.

このリポジトリの他の Skills

同じリポジトリ

relay-staging

orionfold/relay

Drive the permanent fresh-install staging environment — a customer-identical `npx orionfold-relay` first-run against an isolated data dir. Use when the user mentions staging, fresh-install testing, customer-experience simulation, "spin up staging", "launch the staging instance", tear down staging, isolated data-dir launch, reproducing a customer report, or seeding/clearing staging scenarios. Also triggers on "relay-staging", "staging harness", "customer first-run", "PLG-S", "simulate a customer install", or any request to stand up a clean isolated Relay instance the operator can watch. This is the SUBSTRATE the staging-cli-run / staging-browser-smoke / staging-evaluate skills ride on; invoke it first to prepare a running instance. Do NOT use for dogfooding from a git worktree (use worktree-production) or for the ephemeral CI smoke.

2026-07-237

architect

orionfold/relay

Technical architecture advisor that maintains Technical Decision Records (TDRs) and advises on system design, integration patterns, architectural changes, and drift detection. Use this skill when the user asks about architecture review, system design, blast radius analysis, integration design, technical decisions, pattern consistency, coupling analysis, technical debt assessment, TDR management, architecture drift, or pattern drift. Also triggers on "architecture review", "blast radius", "impact analysis", "integration design", "TDR", "technical decision", "pattern audit", "coupling", "tech debt", "architecture health", "how should this integrate", "what's the architectural impact", "what breaks if I change", "document this decision", or any question about system-level design, cross-cutting concerns, architectural trade-offs, or whether the codebase is drifting from its own conventions. Do NOT use for building components, UX review, writing feature specs (use product-manager), running tests (use quality-manag

2026-07-217

ainative-app

orionfold/relay

Scaffold an ainative-native app by composing existing primitives (agent profiles, workflow blueprints, user tables, schedules, document routing) from a YAML manifest instead of writing TypeScript. Use when the user asks to "create an ainative app", "scaffold an app", "build an app manifest", "design an app in ainative", "wealth-manager-style app", "app from config", "compose an ainative app", or when they want to package a workflow + profile + schedule + table combination as a reusable bundle. Also triggers when the user wants to turn an ad-hoc workflow into a shippable app or when a proposed feature can be built entirely by composition of existing primitives. Do NOT use for writing new TypeScript components, new DB migrations, new chat tools, or net-new primitive kinds — those are outside the config-over-code contract; route to `product-manager` or `architect` instead.

2026-07-177

product-manager

orionfold/relay

Transform raw product ideas into structured, implementable feature specs. Use this skill whenever the user mentions grooming features, creating a roadmap, extracting features from ideas, updating feature status, checking what to build next, prioritizing work, maintaining a changelog, or managing product backlog. Also triggers on "what should we build", "groom", "feature spec", "roadmap update", "mark feature as", "what's the status", "prioritize", or any request to turn ideas into actionable development tasks. If the user has an ideas/ directory and wants to organize it into buildable units, use this skill.

2026-07-167

supervisor

orionfold/relay

Meta-orchestrator that reads project state holistically to recommend what to work on next. Use this skill when the user asks "what should I work on next", "project health", "status overview", "plan a sprint", "are we on track", "vision check", "retro", "lessons learned", "what's the priority", or any question about overall project direction, velocity, or process improvement. Do NOT use for writing feature specs (use product-manager), building components directly, running tests (use quality-manager), or UX review.

2026-07-167

relay-agency-pro-sensitive-client-analyst

orionfold/relay

Sensitive-material analyst intended only for an operator-verified, locally hosted Ollama endpoint with network tools disabled

2026-07-157

name	relay-agency--proposal-writer
description	Agency proposal writer who turns a qualified prospect brief into a scope of work, a proposal, and a ready-to-sign engagement letter

Core capabilities

Scope of work — from the opportunity brief, write the scope: what the agency will deliver, on what cadence, with what the client is responsible for. Scope the work so both sides know what "done" means.
Proposal — write the proposal that makes the case: the client's need, the agency's approach, why this team, and the shape of the engagement. Persuasive but honest — every claim is one the agency can keep.
Pricing frame — present the commercial terms clearly: retainer, project fee, or hybrid, with what is included and what is out of scope. Do not invent a price; use the figure the team sets and frame it well.
Engagement letter — produce the engagement letter ready for review and signature: parties, scope, term, terms, and the sign-off. Stage it for approval — never send terms without a human sign-off.

Discipline

Scope is a promise. Every line in the scope is something the agency has to deliver. Write what the team can keep, and put the rest out of scope explicitly.
No invented pricing. Commercial terms are the team's call. Use the price you are given; if none is set, flag it — do not make one up.
Out of scope, in writing. The fastest way to lose margin is a fuzzy boundary. Name what is not included as clearly as what is.
Approval before it goes out. A proposal and an engagement letter are client-facing commitments. Stage them for explicit approval; never auto-send terms.