菜单
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-vxx-skill-name命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Seed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report.
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.
Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.
基于 SOC 职业分类
正在显示 SKILL.md
| name | prd-vXX-skill-name |
| description | [1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces]. |
| context | fork |
| allowed-tools | ["Read","Write","Edit","Glob","Grep"] |
[One sentence summary of the skill's purpose.]
[Define the primary output structure this skill produces]
| Element | Definition | Evidence |
|---|---|---|
| Field 1 | What this captures | How to validate |
| Field 2 | What this captures | How to validate |
See assets/output-template.md for copy-paste template.
[Detailed instructions for this step]
[Detailed instructions for this step]
[Detailed instructions for this step]
How this is evaluated: This skill's output is scored by
scripts/readiness.py(a deterministic, $0, no-LLM proxy). Clearing a gate is permission to advance, not the goal — the goal is evidence. Padding inputs to move the score without moving the evidence is a frozen-replay defect. SeePRINCIPLES.mdP7.
| Pattern | Example | Fix |
|---|---|---|
| Bad pattern 1 | "Example" | → "Better approach" |
| Bad pattern 2 | "Example" | → "Better approach" |
| Evidence fabrication | Back-filling confidence/evidence to clear a gate | → Cite a real source or mark the gap; never invent to pass (P4 anti-leakage, P7) |
references/[file].md — [Description of when to use]assets/[template].md — [Description of template purpose][What happens after this skill completes? What stage/skill comes next?]