Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Agent skill
Prd V09 Launch Channels Orb
by mattgierhart in mattgierhart/PRD-driven-context-engineering
Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market.
Install Prd V09 Launch Channels Orb
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orb --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .claude/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .claude/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orbType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orb --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .agents/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .agents/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orb --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .cursor/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .cursor/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mattgierhart/PRD-driven-context-engineering.git --path .claude/skills/prd-v09-launch-channels-orb--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orb --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .gemini/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .gemini/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orbInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .github/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .github/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v09-launch-channels-orb --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prd-v09-launch-channels-orb .opencode/skills/prd-v09-launch-channels-orb && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prd-v09-launch-channels-orb" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v09-launch-channels-orb into .opencode/skills/prd-v09-launch-channels-orb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v09-launch-channels-orb", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
prd-v09-launch-channels-orb- GitHub stars
- 180
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,145 words
- Files
- 1
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- MIT
At a glance
Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market.
- Works in 7 steps: Map the best-fit segment's channels → Audit your existing assets → Pick channels per layer [standard+] → …
- Requests to pick launch channels
- SKILL.md covers Execution Mode, Framework: Owned / Rented /…, Consumes and Produces, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prd V09 Launch Channels Orb is an agent skill from mattgierhart/PRD-driven-context-engineering. Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Triggers on requests to pick launch channels, distribute the offer, build a channel portfolio, or when user asks "where do we launch?", "what channels?", "ORB", "owned vs rented vs borrowed", "channel allocation", "channel mix", "Corey Haines launch". Outputs GTM- entries with Type=Channel, a channel-mix matrix, and a launch sequence.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering PRD writing and Go-to-market strategy. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.
When your agent uses it
- Requests to pick launch channels
- Distribute the offer
- Build a channel portfolio
- User asks where do we launch?
Example prompts
- “where do we launch?”
- “what channels?”
- “owned vs rented vs borrowed”
- “/prd-v09-launch-channels-orb”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrepWebSearchWebFetch
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Prd V09 Launch Channels Orb loads about 2.8k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 1,145 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 1,145 words, ~2,834 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-v09-launch-channels-orb/SKILL.md (or your agent's skills folder).- name
- prd-v09-launch-channels-orb
- description
- Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Triggers on requests to pick launch channels, distribute the offer, build a channel portfolio, or when user asks "where do we launch?", "what channels?", "ORB", "owned vs rented vs borrowed", "channel allocation", "channel mix", "Corey Haines launch". Outputs GTM-* entries with Type=Channel, a channel-mix matrix, and a launch sequence.
- allowed-tools
- Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
- context
- fork
- execution_modes.default
- standard
- execution_modes.supports
- quick, standard, deep
Launch Channels (ORB: Owned / Rented / Borrowed)
Position in workflow: v0.9 Offer Construction (Hormozi) → v0.9 Launch Channels (ORB) → v0.9 Launch Metrics
Execution Mode
Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.
| Mode | What this skill produces |
|---|---|
| quick | 1 channel per layer (3 channels total); single-week sequence |
| standard | 2–3 channels per layer; pre-launch / launch / post-launch sequence; attribution plan per channel |
| deep | Full portfolio; per-channel content strategy; budget allocation; per-channel ROI projection; channel-mix risk register |
Framework: Owned / Rented / Borrowed (ORB)
ORB classifies every distribution channel by who controls the audience. The rule: own the relationship, rent the platform, borrow the reach — and balance the portfolio so no single channel can take you out.
| Layer | Definition | Examples | Cost | Compounding |
|---|---|---|---|---|
| Owned | You control the audience and the channel | Email list, website, product itself, blog you host, customer base | Time + tools | High — every additional list member compounds future launches |
| Rented | You build presence on someone else's platform | Twitter/X, LinkedIn, YouTube, Slack/Discord communities, podcasts you host | Time | Medium — platform changes rules; audience is portable but messy |
| Borrowed | You access someone else's audience temporarily | Press, podcast guesting, influencers, paid acquisition, integrations, partnerships, affiliate | Money or favor | Low — one-time reach unless converted to Owned/Rented |
The Channel Allocation Principles
- Build Owned before launch, rent through launch, borrow at launch. Without an owned audience, the launch is a one-shot dependent on borrowed reach.
- Pick channels your best-fit segment already uses. Pulled from the Positioning best-fit characteristics — not from "what's popular this quarter."
- One channel per layer to start. Too many channels at once = no signal which is working. Add channels by tier 2–3 only once tier-1 attribution is clean.
- Convert Borrowed → Owned aggressively. Every press hit, podcast guest spot, or partnership should funnel to an owned channel (email signup, demo request) — otherwise it's vanity reach.
- Borrowed scales reach; Owned scales repeat. A launch is a moment; the goal is a list.
Consumes
- GTM-* positioning statement (from v0.9 Positioning) — Best-fit characteristics define where this segment actually spends time
- GTM-* offer card (from v0.9 Offer Construction) — The unit being distributed; channels must accommodate the offer's complexity
- PER-* personas (sharpened by Positioning) — Channel behavior data
- BR-* product type (from v0.2) — Clone/Innovation/Slice/Wrapper channel mixes differ: Clone leans Borrowed-paid, Innovation leans Owned-content, Slice leans Rented-community
- KPI-* baseline targets (from v0.3 Outcome Definition) — Per-channel attribution targets must roll up to baseline KPIs
- DEP-* release readiness (from v0.8) — Channels only fire after DEP- criteria met
Produces
- GTM-* with Type=Channel (one per channel) — Channel name, layer (O/R/B), best-fit fit rationale, content plan, attribution plan, owner, timeline phase
- GTM-* channel-mix matrix (one entry) — Portfolio summary: which channels in which phase, with budget/effort allocation
- GTM-* with Type=Sequence — Pre-launch / launch / post-launch channel firing order
Execution
Step 1: Map the best-fit segment's channels
From the Positioning best-fit characteristics, list where this segment is right now. Be specific:
- Owned channels they already subscribe to (newsletters, podcasts)
- Rented platforms they actively use (with handles / community names)
- Borrowed sources they trust (publications, influencers, conferences)
Do not guess. If you don't know, that's a CFD- research gap.
Step 2: Audit your existing assets
What do you already have in each ORB layer?
| Layer | Asset | Reach (est.) | Activation | Notes |
|---|---|---|---|---|
| Owned | Email list | |||
| Owned | Existing customers | |||
| Rented | Founder Twitter | |||
| Rented | Company LinkedIn | |||
| Borrowed | Press relationships | |||
| Borrowed | Partner integrations |
This audit reveals leverage — most launches over-rely on Borrowed because they have no Owned to lean on. Honest audit prevents that.
Step 3: Pick channels per layer [standard+]
| Mode | Owned | Rented | Borrowed |
|---|---|---|---|
| quick | 1 | 1 | 1 |
| standard | 2–3 | 2–3 | 2–3 |
| deep | Full portfolio | Full portfolio | Full portfolio |
For each candidate channel, score:
- Fit: Does best-fit segment actually use this? (1–5)
- Reach: How many of them does this channel touch? (Est.)
- Effort: What's the time cost per launch wave? (Hours)
- Cost: Direct $ cost?
- Attribution: Can we measure conversion from this channel?
Drop any candidate below Fit 3/5 — no channel is worth it if best-fit doesn't show up there.
Step 4: Sequence the launch
Three phases:
| Phase | Timeline | Channels active | Purpose |
|---|---|---|---|
| Pre-launch | T-30 to T-1 | Owned + Rented (warm) | Build anticipation, grow list |
| Launch | T-0 to T+7 | All three (Borrowed peaks here) | Maximum reach |
| Post-launch | T+7 to T+30 | Owned + Rented (sustain) | Convert reach to relationship |
Quick mode collapses this to a single week. Deep mode extends to 90 days with explicit content per phase.
Show full SKILL.md (430 more words)Show less
Step 5: Plan per-channel attribution
Every channel gets an attribution plan that ties to KPI-:
| Channel | UTM / tracking | KPI- attribution target | Conversion event |
|---|---|---|---|
| Owned: Email | utm_source=email | KPI-XX signup | clicked email → reached offer page |
| Rented: Twitter | utm_source=twitter | KPI-XX signup | clicked tweet → reached offer page |
| Borrowed: PH | utm_source=producthunt | KPI-XX signup | PH referrer → reached offer page |
If a channel can't be attributed, demote it to "supporting" status (still useful for context, but don't count it).
Step 6: Convert Borrowed → Owned [standard+]
For every Borrowed channel, define the next step that converts to Owned. Examples:
- Press hit → article includes "join our list for [bonus]"
- Podcast guest → custom URL with email opt-in
- Product Hunt launch → "early-access list" signup as primary CTA, not "buy now"
If a Borrowed channel has no conversion-to-Owned plan, the launch is leaking value.
Step 7: Build the channel-mix matrix
A single GTM-* entry summarizing the portfolio. See output template below.
Output Template
GTM-XXX: Channel — [Channel Name]
Type: Channel
Layer: [Owned | Rented | Borrowed]
Owner: [Person / team]
Status: [Planned | Active | Live]
Channel: [Specific platform or property]
Best-fit fit: [Why this channel reaches PER-XXX — anchored in Positioning best-fit characteristics]
Fit score: X/5
Reach estimate: [#]
Effort per wave: [Hours]
Cost: [$]
Attribution: [Tracking method, e.g., utm_source=...]
Content plan:
Pre-launch: [What goes out, when, what messaging]
Launch: [...]
Post-launch: [...]
Conversion-to-Owned [if Borrowed]: [How this channel funnels to email list / signup]
Linked IDs: PER-XXX (segment), GTM-YYY (positioning), GTM-ZZZ (offer), KPI-AAA (attribution target)GTM-XXX: Channel-Mix Matrix
Type: Sequence
Status: Approved
Pre-launch (T-30 to T-1):
Owned: GTM-AAA (email), GTM-BBB (blog)
Rented: GTM-CCC (Twitter)
Borrowed: — (none active yet)
Launch (T-0 to T+7):
Owned: GTM-AAA, GTM-BBB
Rented: GTM-CCC, GTM-DDD (LinkedIn)
Borrowed: GTM-EEE (Product Hunt), GTM-FFF (Press)
Post-launch (T+7 to T+30):
Owned: GTM-AAA (drip sequence)
Rented: GTM-CCC (results / social proof posts)
Borrowed: GTM-FFF (case study placements)
Total budget: $X (Borrowed: $X; Rented tools: $Y; Owned: $Z)
Total effort: X hours/week pre-launch; Y hours during launch week
Linked IDs: GTM-YYY (positioning), GTM-ZZZ (offer), DEP-AAA (release readiness), KPI-BBB (attribution rollup)Anti-Patterns
| Pattern | Signal | Fix |
|---|---|---|
| Borrowed-only launch | "We'll launch on Product Hunt and Twitter" with no email list | Build Owned for 30+ days pre-launch or accept the one-shot risk |
| All channels at once | 8 channels in launch week, no idea which worked | Cut to 1 per layer until attribution is clean |
| Channels not used by best-fit | "We should be on TikTok" when segment is on LinkedIn | Drop the channel; segment fit > channel popularity |
| No conversion path | Press hit drives traffic to a homepage with no CTA | Every Borrowed channel needs an email-capture CTA |
| Sequence flattening | All channels fire on launch day | Pre-launch matters — borrow only after Owned and Rented are warm |
| Vanity reach | "We got 50k impressions" but no signups | Drop the channel or fix attribution |
Quality Gates
Before proceeding to Launch Metrics:
- At least one channel per layer (Owned + Rented + Borrowed), each with Fit ≥ 3/5
- Every channel traces to best-fit characteristics from Positioning
- Every channel has an attribution plan (UTM or equivalent)
- Every Borrowed channel has a defined conversion-to-Owned path
- Sequence covers pre-launch, launch, post-launch phases (standard+)
- Channel-mix matrix GTM-* entry exists and references all channel GTM-* entries
Downstream Connections
| Consumer | What it uses | Example |
|---|---|---|
| Launch Metrics | Per-channel attribution targets become KPI- entries | Per-channel UTM → KPI-channel-signups |
| Feedback Loop Setup | Active channels become feedback sources | Twitter mentions → CFD- entries |
| v0.9 Tactical playbooks | AEO audit, alternatives pages, cold outreach, HN/Reddit launch all attach to specific channels named here | Channel = AEO target |
| v1.0 Crossing the Chasm (Moore) | Channel mix shifts per adoption stage | Early-adopter channels ≠ early-majority channels |
Detailed References
- Corey Haines, Marketing Skills repo —
launchskill (ORB classification) - Joe Pulizzi, Content Inc. (Owned-first compounding)
- (No bundled
references/— read source skills for depth)
© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/prd-v09-launch-channels-orb of mattgierhart/PRD-driven-context-engineering.
Open the folder on GitHubat commit 30ed1b0
Compare with similar skills
Prd V09 Launch Channels Orb next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prd V09 Launch Channels Orb this skillmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.8k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 218 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Product Manager SkillsDigidai/product-manager-skills | 185 | — | ~6.1k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| PmLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Management ConsultantDogInfantry/claude-skill-management-consultant-B1 | 136 | — | ~14k | Automated safety check: Pass | Custom licence |
Similar skills
Product Manager Skills
Digidai/product-manager-skills
PM skill for Claude Code, Codex, Cursor, and Windsurf. An agent skill from Digidai/product-manager-skills.
Pm
LeoYeAI/openclaw-master-skills
You are the Product Manager. An agent skill from LeoYeAI/openclaw-master-skills.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Management Consultant
DogInfantry/claude-skill-management-consultant-B1
MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables.
Pre Mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.
More from mattgierhart/PRD-driven-context-engineering
All 45 skills in this repoGhm Gate Check
mattgierhart/PRD-driven-context-engineering
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).
Ghm Harvest
mattgierhart/PRD-driven-context-engineering
Extracts durable insights from temp/ files to SoT during EPIC Phase E.
Ghm Id Register
mattgierhart/PRD-driven-context-engineering
Validates and registers new SoT IDs with cross-reference integrity.
Ghm Sot Builder
mattgierhart/PRD-driven-context-engineering
Creates new Source of Truth (SoT) files when existing templates don't fit your needs.
Prd V01 Problem Framing
mattgierhart/PRD-driven-context-engineering
Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.
Prd V01 User Value Articulation
mattgierhart/PRD-driven-context-engineering
Transform validated pain points into articulated user value statements for PRD v0.1 Spark.
Related
Questions about Prd V09 Launch Channels Orb
What does Prd V09 Launch Channels Orb do?
Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Prd V09 Launch Channels Orb is an agent skill from mattgierhart/PRD-driven-context-engineering.9 Go-to-Market.
When should I use Prd V09 Launch Channels Orb?
Prd V09 Launch Channels Orb fits situations like: requests to pick launch channels; distribute the offer; build a channel portfolio; user asks where do we launch?.
How do I install Prd V09 Launch Channels Orb in Claude Code?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a claude-code`. Or copy the skill folder (.claude/skills/prd-v09-launch-channels-orb in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v09-launch-channels-orb in your project. Claude Code loads it when a task matches its description.
How do I install Prd V09 Launch Channels Orb in Codex?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a codex`. Or copy the skill folder (.claude/skills/prd-v09-launch-channels-orb in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v09-launch-channels-orb in your project. Codex loads it when a task matches its description.
Can I use Prd V09 Launch Channels Orb in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-launch-channels-orb -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v09-launch-channels-orb, .gemini/skills/prd-v09-launch-channels-orb, .github/skills/prd-v09-launch-channels-orb and .opencode/skills/prd-v09-launch-channels-orb in your project.
What does Prd V09 Launch Channels Orb need to run?
SKILL.md names no scripts, command-line tools or credentials: Prd V09 Launch Channels Orb is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, WebSearch, WebFetch.
Does Prd V09 Launch Channels Orb access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Prd V09 Launch Channels Orb safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Prd V09 Launch Channels Orb use?
Prd V09 Launch Channels Orb is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prd V09 Launch Channels Orb use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prd V09 Launch Channels Orb?
Skills that share tags, products or a category with Prd V09 Launch Channels Orb: Plaid (BuildGreatProducts/plaid, 218 stars), Product Manager Skills (Digidai/product-manager-skills, 185 stars), Pm (LeoYeAI/openclaw-master-skills, 2.2k stars) and Organic Growth Path Advisor (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd V09 Launch Channels Orb?
mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.
Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.