本文へ移動
cccskills
無料GitHub で公開

backlog-capture

Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.

mvschwarz/openrig
インストール方法を見る

含まれるファイル（1）

  • SKILL.md2.0 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

You help a product manager rapidly capture ideas, feature requests, and insights into a structured backlog.

When to Use

  • After meetings where feature ideas or requests surfaced
  • When a customer or sales rep mentions a need
  • When competitive research reveals a gap
  • When a PM has a shower thought worth recording

Process

  1. Take the input — the PM provides rough text: a meeting quote, a feature idea, a customer request, a competitive gap.

  2. Structure it — produce a one-liner for the backlog with:

    • Bold name — short, descriptive feature name
    • Description — 1-3 sentences covering: what it is, who it's for, why it matters, where it originated (meeting, customer, competitor)
    • Epic/area — which product area it belongs to
    • Dependencies — if it relates to existing features or backlog items

  3. Check for duplicates — search the existing backlog for similar items. If a match exists:

    • Update the existing item with new evidence rather than creating a duplicate
    • Add the new source/date to the existing description

  4. Append to backlog — add to the "Ideas Not Yet in Jira" section of the backlog file.

Output Format

- **[Feature Name]** — [Description. Who needs it. Why. Origin (meeting/customer/competitor, date).] Belongs under [Epic] epic. [Dependencies if any.]

Guidelines

  • Capture fast, refine later. The goal is not to lose the idea. Polish comes during prioritization.
  • Include the source. "From Acme Corp demo feedback (2026-03-15)" is better than "customers want this."
  • Convert relative dates to absolute. "Next Thursday" becomes "2026-04-10."
  • One idea per entry. If a meeting produced 5 ideas, create 5 entries.
  • Don't validate here. That's what /office-hours is for. Just capture.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

agent-browser

無料

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

agent-operated-software

無料

Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

agent-operated-workflows

無料

Use when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

agent-starters

無料

Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

agent-startup-and-context-ingestion

無料

Use when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, "rig context" surface. Covers the 4 failure modes that make startup context fail (old rig spec misses current operating mode; current agents never told about new guidance; startup file as dumping ground; orchestrator transmits implementation without preserving product intent).

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

applying-a-permission-policy

無料

Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,8042026年10月11日 更新

mvschwarz のスキルをすべて見る

このスキルの問題を報告する