Release
zmievsa/cadwyn
Prepare and publish Cadwyn releases. An agent skill from zmievsa/cadwyn.
Agent skill
Prd V08 Changelog As Marketing
by mattgierhart in mattgierhart/PRD-driven-context-engineering
Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops.
Install Prd V08 Changelog As Marketing
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v08-changelog-as-marketing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v08-changelog-as-marketing --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-v08-changelog-as-marketing .claude/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .claude/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketingType 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-v08-changelog-as-marketing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v08-changelog-as-marketing --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-v08-changelog-as-marketing .agents/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .agents/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v08-changelog-as-marketing --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-v08-changelog-as-marketing .cursor/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .cursor/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketing--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-v08-changelog-as-marketing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v08-changelog-as-marketing --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-v08-changelog-as-marketing .gemini/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .gemini/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketingInstalls 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-v08-changelog-as-marketing -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-v08-changelog-as-marketing .github/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .github/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketing -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-v08-changelog-as-marketing --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-v08-changelog-as-marketing .opencode/skills/prd-v08-changelog-as-marketing && 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-v08-changelog-as-marketing" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v08-changelog-as-marketing into .opencode/skills/prd-v08-changelog-as-marketing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v08-changelog-as-marketing", 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-v08-changelog-as-marketing- GitHub stars
- 180
- Token cost
- ~2.6k tokens
- SKILL.md length
- 959 words
- Files
- 1
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops.
- Works in 6 steps: Define the changelog audience(s) —… → Categorize release content — Each… → Map categories to channels — Each… → …
- Requests to set up a changelog system
- SKILL.md covers Execution Mode, What This Does, How It Works and Example, plus 9 more sections
- Calls git
What it does
Prd V08 Changelog As Marketing is an agent skill from mattgierhart/PRD-driven-context-engineering. Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Triggers on requests to set up a changelog system, publish releases, or when user asks "how should we publish releases?", "changelog as marketing", "release notes", "Stripe-style changelog", "what to do with our release notes", "ship and tell". Outputs MON-CHG- changelog entries and per-channel formats.
Its SKILL.md is about 2.6k 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 Development, covering Changelog and release notes and PRD writing. It works with Stripe. 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 set up a changelog system
- Publish releases
- User asks how should we publish releases?
- Changelog as marketing
Example prompts
- “how should we publish releases?”
- “changelog as marketing”
- “release notes”
- “/prd-v08-changelog-as-marketing”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Define the changelog audience(s) — Engineering changelogs (for users running self-hosted or integrating an API), customer-facing…
- Categorize release content — Each shipped item gets a category
- Map categories to channels — Each category gets a channel destination from the ORB mix
- Build per-channel format templates — Each channel has a length/tone constraint
- Set publish cadence — Per-release (every shipped release publishes immediately) vs. digest (weekly/monthly roll-up). Most teams need both…
- Plan attribution — Every channel-published release gets a UTM. Track changelog → signup conversion to identify which categories convert.
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:
ReadWriteEditGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
stripe.comlinear.appvercel.com
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 V08 Changelog As Marketing loads about 2.6k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 959 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). 959 words, ~2,557 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-v08-changelog-as-marketing/SKILL.md (or your agent's skills folder).- name
- prd-v08-changelog-as-marketing
- description
- Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Triggers on requests to set up a changelog system, publish releases, or when user asks "how should we publish releases?", "changelog as marketing", "release notes", "Stripe-style changelog", "what to do with our release notes", "ship and tell". Outputs MON-CHG-* changelog entries and per-channel formats.
- allowed-tools
- Read, Write, Edit, Glob, Grep
- context
- fork
- execution_modes.default
- standard
- execution_modes.supports
- quick, standard, deep
Changelog as Marketing
Position in workflow: v0.8 Release Planning → v0.8 Changelog as Marketing → v0.9 Launch Channels (ORB)
Execution Mode
Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.
| Mode | What this skill produces |
|---|---|
| quick | One release format (markdown for site); one channel mapping; minimum-viable changelog page |
| standard | Release categorization + 2–3 channel mappings; per-channel format templates; publish cadence; attribution plan |
| deep | Full categorization taxonomy; format templates for all relevant channels (email, blog, Twitter, LinkedIn, RSS, Slack); cadence + voice guide; KPI- attribution per channel |
What This Does
Treats the changelog as a distribution surface, not an engineering record. Each shipped release becomes a content artifact that lands across Owned and Rented channels with minimal extra effort. This is the bridge between v0.8 (what shipped) and v0.9 (where it gets told).
Done well, this is one of the highest-leverage Owned-channel investments — Stripe, Linear, Vercel, and Sentry have shown that an opinionated changelog drives ongoing inbound that compounds over years. Done badly, it's a dumping ground for "fixed bug X" that nobody reads.
How It Works
- Define the changelog audience(s) — Engineering changelogs (for users running self-hosted or integrating an API), customer-facing changelogs (for end-users), and internal changelogs (for the team) have different shapes. Anchor to the Positioning best-fit segment.
- Categorize release content — Each shipped item gets a category:
- New feature (publish loudly)
- Improvement (publish, briefly)
- Breaking change (publish, prominently, with migration path)
- Deprecation (publish, with timeline)
- Fix (publish only if user-visible)
- Internal (don't publish externally)
- Map categories to channels — Each category gets a channel destination from the ORB mix:
- New feature → Blog post + email + Twitter + LinkedIn
- Breaking change → Email (high-priority) + RSS + blog
- Improvement → Blog (digest) + Twitter (digest)
- Fix → Changelog page only
- Build per-channel format templates — Each channel has a length/tone constraint:
- Email: subject line + 2-paragraph body + CTA
- Blog: full writeup, screenshots, code samples
- Twitter/X: 280 chars, one image
- LinkedIn: 1,000-1,500 chars, professional voice
- Slack/Discord: short with link to blog
- RSS: full content for engineering audiences
- Set publish cadence — Per-release (every shipped release publishes immediately) vs. digest (weekly/monthly roll-up). Most teams need both: per-release for big things, digest for the rest.
- Plan attribution — Every channel-published release gets a UTM. Track changelog → signup conversion to identify which categories convert.
Example
A developer-tools product ships:
| Item | Category | Channels |
|---|---|---|
New /api/v2/webhooks endpoint | New feature | Blog (full), email, Twitter, LinkedIn, RSS |
/api/v1/webhooks deprecation (sunset in 6mo) | Deprecation | Email (high-priority), blog, RSS |
| 30% faster response time on heavy queries | Improvement | Twitter, weekly digest |
| Fixed: webhook signing edge case | Fix | Changelog page only |
| Internal: refactored auth middleware | Internal | (none) |
Tuesday publish:
- Blog post: "Webhooks v2 is live — here's what changed and how to migrate"
- Email to API customers (segment-targeted, not full list): "Action needed: webhook v1 sunset"
- Twitter: "Webhooks v2 ships today. v1 is sunset in 6 months. Migration guide: [link]"
- Changelog page: all five items (including the fix and internal note marked appropriately)
What You Get Back
- MON-CHG-* changelog entries (one per shipped release) — Master record with category, audience, channel mapping, links to per-channel publications
- GTM-CHG-* per-channel formats (one per channel) — Templates and example content
- Publish cadence schedule — Per-release vs. digest decisions
- KPI attribution plan — UTMs and conversion tracking
When to Use It
| Trigger | Mode |
|---|---|
| First release post-launch (no changelog system yet) | quick |
| Standard launch cadence stabilizing | standard |
| Pre-investor / pre-Series A — changelog as proof of velocity | deep |
| API or developer-tool product | deep (changelog is a primary surface) |
| One-time announcements (acquisition, big feature) | standard |
Show full SKILL.md (391 more words)Show less
Consumes
- DEP-* release entries (from v0.8 Release Planning) — What's being released, when
- FEA-* features (from v0.3) — What new features exist; categorization input
- GTM-* channel mix (from v0.9 Launch Channels ORB, when available) — Where to publish
- GTM-* positioning (from v0.9 Positioning, when available) — Voice and tone constraints
- PER-* best-fit characteristics — Audience tone calibration
- KPI-* baselines — Attribution targets
When this skill runs before v0.9 has executed, channel mapping uses placeholder channels and is reconciled when v0.9 channels are finalized.
Produces
- MON-CHG-* entries in
SoT/SoT.DEPLOYMENT.md(or a dedicatedSoT/SoT.CHANGELOG.mdif release volume warrants) - GTM-CHG-* entries with
Type=Channel-Changelog(per-channel format templates) - CFD-* gaps surfaced — If a release category lacks an obvious channel mapping, log as research gap
Output Template
MON-CHG-XXX: Release — [Release name / version]
Type: Changelog
Date: YYYY-MM-DD
Owner: [Person / role]
Status: [Drafted | Reviewed | Published]
Released items:
- [Item 1] — Category: [New feature | Improvement | Breaking change | Deprecation | Fix | Internal]
- [Item 2] — Category: ...
Audience: [API customers | All users | Internal team | Mixed]
Channel publications:
- Blog: [URL or "scheduled YYYY-MM-DD"]
- Email: [Segment + scheduled date]
- Twitter: [Scheduled date]
- LinkedIn: [Scheduled date]
- Changelog page: [Updated YYYY-MM-DD]
Attribution: utm_campaign=changelog-<version>
Linked IDs: DEP-AAA (release), FEA-BBB (features shipped), GTM-CHG-CCC (channel formats), KPI-DDD (attribution)GTM-CHG-XXX: Channel Format — [Channel name]
Type: Channel-Changelog
Channel: [Blog | Email | Twitter | LinkedIn | RSS | Slack]
Owner: [Person / role]
Format constraints:
Length: [chars / words / sections]
Tone: [Conversational | Technical | Formal — anchored in Positioning voice]
Visuals: [Required / optional]
CTA: [Specific action expected]
Template:
[Reusable template for this channel, with variable placeholders]
Example (most recent use):
[Concrete example from MON-CHG-XXX]
Publish trigger: [Per-release | Weekly digest | Monthly digest]
Linked IDs: MON-CHG-AAA (latest use), GTM-YYY (positioning voice)Anti-Patterns
| Pattern | Signal | Fix |
|---|---|---|
| Dumping internal commits | Changelog reads like git log | Categorize; publish only what users care about |
| Same content everywhere | Same blog post copy-pasted to Twitter and LinkedIn | Each channel has its own format constraints; honor them |
| Vague feature claims | "Various improvements" | Name the specific change; "30% faster heavy queries" beats "performance improvements" |
| Engineering-only voice | Customer changelog uses internal jargon | Tone-shift per audience; engineer changelog ≠ end-user changelog |
| No attribution | Changelog publishes but no idea what converts | UTM every link; track per-channel conversion |
| Sporadic cadence | Publish heavily for 2 months, then quiet for 6 | Pick per-release or digest cadence; commit to it |
| Breaking change buried | Hidden in a sea of small items | Breaking changes get a dedicated, prominent slot |
Quality Gates
Before publishing the first release:
- Audience(s) defined (engineering, customer-facing, internal — separately if needed)
- Categorization scheme exists (at minimum: new / improvement / breaking / fix)
- Channel mapping table exists (categories → channels)
- Per-channel format templates exist
- Publish cadence committed
- Attribution plan (UTM convention) defined
- Voice/tone honors GTM- positioning (if v0.9 is done)
Downstream Connections
| Consumer | What it uses | Example |
|---|---|---|
| Launch Channels (ORB) | Changelog is an Owned channel; rolls into mix matrix | Blog-changelog = Owned-content |
| Launch Metrics | Per-channel changelog conversion targets | KPI-changelog-blog-signups |
| Feedback Loop Setup | Changelog reader comments become CFD- | Blog comment threads → CFD- pattern |
| AEO Audit | High-traffic changelog posts become AI citation sources | Changelog entries cited by AI search |
| v1.0 Case Study Builder | Shipped features in changelog feed case study material | "How we use [feature] at [customer]" |
Detailed References
- Stripe changelog: stripe.com/changelog — the canonical example
- Linear changelog: linear.app/changelog — opinionated voice
- Vercel changelog: vercel.com/changelog — visual-heavy
- jonathimer's
changelog-updatesskill (devmarketing-skills) - (No bundled
references/— read the source examples for current best practice)
© 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-v08-changelog-as-marketing of mattgierhart/PRD-driven-context-engineering.
Open the folder on GitHubat commit 30ed1b0
Compare with similar skills
Prd V08 Changelog As Marketing 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 V08 Changelog As Marketing this skillmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Releasezmievsa/cadwyn | 309 | — | ~522 | Automated safety check: Pass | MIT | |
| Ad Archivealexandremendoncaalvaro/CorridorKey-Runtime | 756 | 1 repos | ~1.6k | Automated safety check: Pass | Custom licence | |
| Developer Docs Technical Researchhashgraph-online/awesome-codex-plugins | 1.3k | — | ~841 | Automated safety check: Pass | MIT | |
| Dj Prefixed Ulidsdvf/opinionated-django | 109 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Workflowwaynesutton/markdown-site | 627 | — | ~624 | Automated safety check: Pass | MIT |
Similar skills
Ad Archive
alexandremendoncaalvaro/CorridorKey-Runtime
Sweep completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) out of the working tree and into git history via git rm.
Developer Docs Technical Research
hashgraph-online/awesome-codex-plugins
Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes.
Dj Prefixed Ulids
dvf/opinionated-django
Use Stripe-style prefixed ULID primary keys (e.g. An agent skill from dvf/opinionated-django.
Workflow
waynesutton/markdown-site
Project workflow for PRDs, task tracking, changelog sync, and documentation updates.
Herdr Pre-Release Audit
herdrdev/herdr
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…
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
Works with
Categories
Questions about Prd V08 Changelog As Marketing
What does Prd V08 Changelog As Marketing do?
Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Prd V08 Changelog As Marketing is an agent skill from mattgierhart/PRD-driven-context-engineering.8 Deployment & Ops.
When should I use Prd V08 Changelog As Marketing?
Prd V08 Changelog As Marketing fits situations like: requests to set up a changelog system; publish releases; user asks how should we publish releases?; changelog as marketing.
How do I install Prd V08 Changelog As Marketing in Claude Code?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v08-changelog-as-marketing -a claude-code`. Or copy the skill folder (.claude/skills/prd-v08-changelog-as-marketing in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v08-changelog-as-marketing in your project. Claude Code loads it when a task matches its description.
How do I install Prd V08 Changelog As Marketing in Codex?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v08-changelog-as-marketing -a codex`. Or copy the skill folder (.claude/skills/prd-v08-changelog-as-marketing in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v08-changelog-as-marketing in your project. Codex loads it when a task matches its description.
Can I use Prd V08 Changelog As Marketing 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-v08-changelog-as-marketing -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-v08-changelog-as-marketing, .gemini/skills/prd-v08-changelog-as-marketing, .github/skills/prd-v08-changelog-as-marketing and .opencode/skills/prd-v08-changelog-as-marketing in your project.
What does Prd V08 Changelog As Marketing need to run?
Going by SKILL.md and its folder, Prd V08 Changelog As Marketing needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep.
Does Prd V08 Changelog As Marketing access the network?
SKILL.md names 3 domains. As links in the text: stripe.com, linear.app and vercel.com. This is read from the text; nothing was executed.
Is Prd V08 Changelog As Marketing 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 V08 Changelog As Marketing use?
Prd V08 Changelog As Marketing 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 V08 Changelog As Marketing use?
About 2.6k tokens (SKILL.md is roughly 10k 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 V08 Changelog As Marketing?
Skills that share tags, products or a category with Prd V08 Changelog As Marketing: Release (zmievsa/cadwyn, 309 stars), Ad Archive (alexandremendoncaalvaro/CorridorKey-Runtime, 756 stars), Developer Docs Technical Research (hashgraph-online/awesome-codex-plugins, 1.3k stars) and Dj Prefixed Ulids (dvf/opinionated-django, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd V08 Changelog As Marketing?
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.