メニュー
Create a product roadmap (Now / Next / Later) in 07-strategy/roadmaps/ from the roadmap template. Use when the user wants to start, draft, or plan a roadmap for a horizon, quarter, or half. Pass the roadmap name/horizon as args (e.g. "Payments H2 2026").
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 | roadmap-new |
| description | Create a product roadmap (Now / Next / Later) in 07-strategy/roadmaps/ from the roadmap template. Use when the user wants to start, draft, or plan a roadmap for a horizon, quarter, or half. Pass the roadmap name/horizon as args (e.g. "Payments H2 2026"). |
Create a roadmap in the strategy area.
Read paths.roadmaps (default 07-strategy/roadmaps), paths.strategy (default
07-strategy), owner.slug, and context.team from .agents/config.yaml.
2026-h2 when args names a period.{slug}.md already exists in {paths.roadmaps}/ (offer to open it
instead of overwriting). Create the {paths.roadmaps}/ folder if it doesn't exist._templates/roadmap.md.{paths.roadmaps}/{slug}.md from the template with frontmatter filled:
title: from argsslug: the slugstatus: activeowner: {{owner_slug}} resolved from configteam: {{team}} resolved from confighorizon: the parsed horizon (else leave as a prompt)last_reviewed: today's dateprojects: if args or context clearly names initiatives that map to existing project
slugs, set them as an array (validate each exists in paths.projects); otherwise leave
[]. A populated projects: makes the roadmap surface in those projects' hub rollups
under Strategy on the next project-sync.## Revision log.{paths.strategy}/_index.md.- [ ] Fill in roadmap: {title} #follow-up to the current week's active file in
01-weekly/.Output the created file path. If projects: was set, note it will surface in those hubs on the
next project-sync.