菜单
Create a Product Requirements Document (PRD) in a project's docs/ from the prd template. Use when the user wants to write, draft, or start a PRD, product spec, or requirements doc for a feature or initiative. Pass the PRD title and/or its project as args (e.g. "Guest checkout for payments-platform").
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a new GitHub issue (optionally added to a GitHub Project board) following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via the `gh` CLI. Use when the user wants to file, open, or create a GitHub issue. Optionally pass the repo and/or issue title as args.
Explore a remote GitHub repository read-only via the `gh` CLI — search code, read a file at a ref, view repo structure, trace the history/PRs touching a path, and blame lines. Use when investigating an incident or working an assignment against code you don't have checked out, across one or more repos. Pass the repo(s) (`owner/repo`) and what you're looking for as args.
Fetch a GitHub pull request as a structured bundle (metadata, diff, changed files with stats, commits, CI/check status, and existing review comments) via the `gh` CLI. Transport-only — it retrieves, it does not judge. Used by the tool-agnostic `pr-review` skill; you normally won't invoke it directly. Pass a PR number, URL, or branch (and optionally `owner/repo`) as args.
Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args.
Do a first-line review pass on a pull request — summarize the changes, flag obvious issues, highlight architectural/dependency changes, and escalate what needs human attention. It hands you structured input to act on; it does NOT auto-approve or post to the code host. Use when the user wants a PR reviewed, triaged, or summarized before they dig in. Pass a PR number, URL, or branch as args.
Import any document by URL into emOS. Detects the transport (Confluence, Google Docs, GitHub, or a generic web page), delegates to the medium-specific provider skill when its capability is configured, classifies the content, files it, and pulls any action items assigned to the owner into the current week's plan. Use when the user gives a URL and wants its content brought into the vault. Pass the URL (and optionally a hint about the doc type) as args.
| name | prd-new |
| description | Create a Product Requirements Document (PRD) in a project's docs/ from the prd template. Use when the user wants to write, draft, or start a PRD, product spec, or requirements doc for a feature or initiative. Pass the PRD title and/or its project as args (e.g. "Guest checkout for payments-platform"). |
Create a PRD as a project-local doc.
Read paths.projects (default 03-projects) and owner.slug from .agents/config.yaml.
{paths.projects}/. If none is stated, ask which project this PRD is for; if the project
doesn't exist yet, offer to run project-new first._templates/prd.md.{paths.projects}/{project-slug}/docs/prd.md if the project has no PRD
yet; otherwise {paths.projects}/{project-slug}/docs/prd-{feature-slug}.md. Create the
docs/ folder if it doesn't exist.title: from argsslug: the feature slugstatus: draftowner: {{owner_slug}} resolved from configprojects: the parent project slug (this is a human pointer to the parent, not a rollup
key — the PRD already lives inside the project folder)jira_epic, target_date, tags as prompts/empty- [ ] Draft PRD: {title} #follow-up #project/{project-slug} to the current week's
active file in 01-weekly/.Output the created file path and the parent project. Note that the PRD lives in the project's
docs/ and is browsable from the project folder.