CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model.
Install Prd V03 Moat Definition
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-moat-definition -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v03-moat-definition --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-v03-moat-definition .claude/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .claude/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definitionType 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-v03-moat-definition -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v03-moat-definition --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-v03-moat-definition .agents/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .agents/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definition -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v03-moat-definition --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-v03-moat-definition .cursor/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .cursor/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definition--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-v03-moat-definition -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v03-moat-definition --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-v03-moat-definition .gemini/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .gemini/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definitionInstalls 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-v03-moat-definition -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-v03-moat-definition .github/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .github/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definition -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-v03-moat-definition --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-v03-moat-definition .opencode/skills/prd-v03-moat-definition && 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-v03-moat-definition" agent skill from https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-moat-definition into .opencode/skills/prd-v03-moat-definition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-v03-moat-definition", 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-v03-moat-definition- GitHub stars
- 180
- Token cost
- ~2.3k tokens
- SKILL.md length
- 771 words
- Files
- 4 (incl. references, assets)
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model.
- Works in 6 steps: Pull Competitor Data → Identify Moat Type → Rate Moat Strength → …
- Requests to analyze competitor moats
- SKILL.md covers Consumes, Produces, Moat Type Taxonomy and Moat Strength Tiers, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prd V03 Moat Definition is an agent skill from mattgierhart/PRD-driven-context-engineering. Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/br-targeting.md`, `assets/cfd-moat-analysis.md` and `references/examples.md`).
It sits in Product & Project Management, covering PRD writing and Physical and earth sciences. 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 analyze competitor moats
- Define our defensibility
- Assess switching costs
- Identify vulnerabilities
Example prompts
- “s our moat?”
- “how defensible are they?”
- “where can we compete?”
- “/prd-v03-moat-definition”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
Workflow steps
6 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 (its code samples are markdown).
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 V03 Moat Definition loads about 2.3k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 771 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). 771 words, ~2,346 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-v03-moat-definition/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- prd-v03-moat-definition
- description
- Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.
- allowed-tools
- Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
- context
- fork
Moat Definition
Position in HORIZON workflow: v0.2 Competitive Landscape → v0.3 Moat Definition → v0.3 Pricing Model Selection
Consumes
This skill requires prior work from v0.2:
- Landscape map artifact (from Competitive Landscape Mapping) — Current behavior documentation, feature matrix, competitor analysis
- CFD-* entries (competitive intelligence, from Competitive Landscape Mapping) — Documented competitors with pricing, features, user feedback
- BR-* product type entry (from Product Type Classification) — Classification constrains which competitors are relevant to analyze
This skill assumes v0.2 analysis is complete with documented competitors.
Produces
This skill creates/updates:
- CFD-* entries (competitor moat analysis) — Assessment of each competitor's defensibility by moat type
- BR-* entries (targeting rules) — Constraints derived from moat analysis, defining where to compete vs. avoid
- Moat strength inventory artifact — Summary of competitor moats with vulnerability signals
All CFD moat analysis entries should include:
confidence: 2-3/5(based on public evidence + user interviews about switching friction)- Evidence source (pricing pages, reviews, customer interviews)
- Forward target: "Would move to 4/5 if we interview 5+ current/former customers about switching costs"
Example moat analysis entry:
CFD-055: Competitor Moat Analysis — Notion
Competitor: Notion
Primary Moat Type: Switching Costs (data lock-in)
Moat Strength Tier: Strong
Confidence: 3/5 (source: public-research + 2-user-interviews)
Date: 2026-02-01
Switching Cost Quantification:
- Financial: Multi-year contract, no early termination ($0 direct cost)
- Time/Effort: 20+ hours migration, team retraining
- Data Migration: Proprietary database format (complex export)
- Workflow Retraining: Unique templates, team habits
- Integration Rework: Deep Slack/GitHub dependencies
Total Switching Cost: $3K in labor + 20 hours = Material friction
Moat Verdict: Strong — switching costs >$3K + meaningful time investment
Vulnerability Signal: SMB segment with small teams; they use <20% of feature set (opportunity for simpler tool)
Targeting Decision: Avoid direct competition. Wedge in SMB with simplified, cheaper offering.
Evidence:
- CFD-042 (landscape): Reviews show enterprise love; SMB complaints focus on cost + complexity
- CFD-015 (value hypothesis): SMB would save $12,500/year with simpler tool
Next Target: "Would move to 4/5 if we interview 5+ SMB teams about exact switching cost dollars"Moat Type Taxonomy
Every moat falls into one of six types. Identify primary + secondary moats per competitor:
| Moat Type | Definition | Strong When | Weak When |
|---|---|---|---|
| Switching Costs | Friction to leave (data, workflow, contracts) | Multi-year data, deep integrations | Easy export, monthly contracts |
| Network Effects | Value increases with users | Two-sided marketplace, content platform | Single-player tool, linear value |
| Data/IP | Proprietary data or algorithms | Unique training data, patents | Commodity ML, public datasets |
| Brand/Trust | Recognition, credibility | Regulated industry, high-risk decisions | Low-stakes, undifferentiated |
| Scale/Cost | Volume economics | Infrastructure-heavy, marginal cost near zero | Labor-intensive, linear cost |
| Regulatory | Compliance barriers | Certifications required, government contracts | No compliance requirements |
For micro-SaaS: Switching costs and brand/trust matter most. Network effects and scale rarely apply.
Moat Strength Tiers
Rate each competitor's defensibility:
| Tier | Criteria | Evidence Signals | Targeting Implication |
|---|---|---|---|
| Impenetrable | Multi-layered moat, 10+ years data lock-in | "Would take years to switch" | Avoid direct competition |
| Strong | Significant switching friction, 1-2 year contracts | High NPS + low churn despite complaints | Target underserved segments only |
| Moderate | Some friction, workarounds exist | Churn 5-10%, export options | Wedge opportunity exists |
| Weak | Easy to replace, commodity offering | Monthly plans, high churn, price shopping | Direct competition viable |
| Eroding | Former strength declining | New alternatives gaining share | Aggressive targeting |
Gate rule: Don't compete where incumbent has Impenetrable or Strong moat unless targeting segment they explicitly ignore.
Switching Cost Inventory
Quantify ALL switching costs — the sum determines moat strength:
| Cost Type | High Impact | Low Impact | How to Assess |
|---|---|---|---|
| Financial | >6mo contract, early termination fees | Monthly billing, no penalty | Check pricing page terms |
| Time/Effort | 40+ hr migration, retraining | <4 hr setup, familiar UX | Trial the competitor |
| Data Migration | Proprietary format, no export | Standard export (CSV, API) | Test export function |
| Workflow Retraining | Unique methodology, team habits | Standard patterns | Read onboarding docs |
| Integration Rework | Deep API dependencies | Standalone tool | Map their integrations |
Calculation: Sum hours + dollars. >$5K or >40hr = material switching cost.
Show full SKILL.md (303 more words)Show less
Targeting Decision Framework
Use moat analysis to determine where to compete:
Moat Impenetrable/Strong → DON'T COMPETE HERE
↓ unless
Target ignored segment (SMB, specific vertical)
Moat Moderate → WEDGE STRATEGY
↓ identify
Entry point that bypasses switching friction
Moat Weak/Eroding → DIRECT COMPETITION
↓ execute
Feature + price attack on their coreWedge Opportunity Signals
A wedge exists when:
- Competitor moat doesn't apply to specific segment
- One feature has LOW switching cost (can start there)
- Integration allows coexistence (not replacement)
- Price sensitivity > switching friction
Analysis Workflow
Step 1: Pull Competitor Data
Retrieve CFD- entries from v0.2 Competitive Landscape. For each competitor, you need: pricing, complaints, feature set.
Step 2: Identify Moat Type
For each competitor, determine primary moat type. Use evidence from reviews, pricing structure, integration depth.
Step 3: Rate Moat Strength
Apply tier criteria. Flag if insufficient evidence (Tier 4-5 confidence).
Step 4: Inventory Switching Costs
Complete the 5-category switching cost assessment. Quantify hours + dollars.
Step 5: Identify Vulnerabilities
Where is their moat weakest? Which segments do they ignore? What's eroding?
Step 6: Generate IDs
CFD entries (customer_feedback.md): Template: assets/cfd-moat-analysis.md
CFD-MOT-###: [Competitor] Moat Analysis — [Moat Type], [Strength Tier]BR entries (BUSINESS_RULES.md): Template: assets/br-targeting.md
BR-TGT-###: [Targeting Rule] — based on [Competitor] moat weaknessAnti-Patterns to Avoid
| Don't | Do Instead |
|---|---|
| "They're big" | Specify which moat type + evidence |
| Assume low switching cost | Quantify: hours + dollars |
| Only analyze direct competitors | Include Type 4-5 (workarounds, inertia) |
| Underestimate integration moat | Map actual dependency depth |
| Ignore eroding moats | Track signals: new entrants, complaints |
| Target where moat is strong | Find the segment where moat doesn't apply |
Output Requirements
Before advancing to Our Moat Articulation:
- ≥3 competitors with moat type identified
- ≥2 competitors with switching costs quantified
- Moat strength tier assigned (with evidence)
- Targeting decision per competitor (compete/avoid/wedge)
- CFD-MOT entries created (≥3)
- BR-TGT entries created (≥2)
Downstream Connections
| Consumer | What It Needs | Format |
|---|---|---|
| v0.3 Our Moat Articulation | Where competitors are weak, what moats work | CFD-MOT entries |
| v0.3 Pricing Model | What price points bypass switching friction | BR-TGT entries |
| v0.5 Red Team | Risks of competitor response | Moat strength tiers |
| v0.9 GTM | Positioning against competitor moats | Targeting rules |
Detailed References
- Good/bad examples: See
references/examples.md - CFD-MOT template: See
assets/cfd-moat-analysis.md - BR-TGT template: See
assets/br-targeting.md
© 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
SKILL.md and 3 other files (references, assets) in .claude/skills/prd-v03-moat-definition of mattgierhart/PRD-driven-context-engineering.
- SKILL.md
- assets/br-targeting.md
- assets/cfd-moat-analysis.md
- references/examples.md
Open the folder on GitHubat commit 30ed1b0
Compare with similar skills
Prd V03 Moat Definition 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 V03 Moat Definition this skillmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.3k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
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
Categories
Questions about Prd V03 Moat Definition
What does Prd V03 Moat Definition do?
Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Prd V03 Moat Definition is an agent skill from mattgierhart/PRD-driven-context-engineering.3 Commercial Model.
When should I use Prd V03 Moat Definition?
Prd V03 Moat Definition fits situations like: requests to analyze competitor moats; define our defensibility; assess switching costs; identify vulnerabilities.
How do I install Prd V03 Moat Definition in Claude Code?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-moat-definition -a claude-code`. Or copy the skill folder (.claude/skills/prd-v03-moat-definition in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v03-moat-definition in your project. Claude Code loads it when a task matches its description.
How do I install Prd V03 Moat Definition in Codex?
Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-moat-definition -a codex`. Or copy the skill folder (.claude/skills/prd-v03-moat-definition in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v03-moat-definition in your project. Codex loads it when a task matches its description.
Can I use Prd V03 Moat Definition 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-v03-moat-definition -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-v03-moat-definition, .gemini/skills/prd-v03-moat-definition, .github/skills/prd-v03-moat-definition and .opencode/skills/prd-v03-moat-definition in your project.
What does Prd V03 Moat Definition need to run?
SKILL.md names no scripts, command-line tools or credentials: Prd V03 Moat Definition is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, WebSearch, WebFetch.
Does Prd V03 Moat Definition 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 V03 Moat Definition 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 V03 Moat Definition use?
Prd V03 Moat Definition 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 V03 Moat Definition use?
About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Prd V03 Moat Definition?
Skills that share tags, products or a category with Prd V03 Moat Definition: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd V03 Moat Definition?
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.