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

prd

Convert current conversation context into a structured Product Requirements Document (PRD) and optionally post it to GitHub Issues. Use before /supergraph:plan when requirements came from a conversation, user story, or feature discussion rather than a formal spec.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

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

/supergraph:prd

Turn conversation into a machine-readable PRD. Gives /supergraph:plan a concrete spec to work from.

Announce: "📋 /supergraph:prd — extracting requirements..."

Steps

1. Read CONTEXT.md (if exists)

head -60 CONTEXT.md 2>/dev/null || echo "No CONTEXT.md"

Use domain vocabulary from CONTEXT.md in the PRD — never invent new terms for existing concepts.

2. Extract requirements from conversation

Gather from current conversation context:

  • What the user wants to accomplish
  • Any constraints or non-goals mentioned
  • Technical decisions already made
  • Edge cases or concerns raised

Ask one clarifying question if a critical piece is missing. Do not ask multiple questions at once.

3. Write PRD

# PRD: [Feature/Fix Name]

## Problem
[One paragraph: what is broken or missing, and why it matters]

## Solution
[One paragraph: the approach — what will be built]

## User Stories
- As a [role], I want [action] so that [outcome]
- (2-5 stories max)

## Acceptance Criteria
- [ ] [Observable, testable condition]
- [ ] [Observable, testable condition]
- (Each maps to a test in /supergraph:plan)

## Implementation Decisions
- [Technology/pattern chosen and why]
- [What was explicitly ruled out and why]

## Testing Decisions
- [Unit: what gets unit tested]
- [Integration: what needs integration tests]
- [E2E: what needs Playwright coverage, if any]

## Out of Scope
- [Explicitly not included in this work]

## Notes
- [Domain terms: add to CONTEXT.md if new]
- [Dependencies on other work]
- [Security considerations]

4. Present for approval

Show PRD to user. Ask: "Does this capture what you need? [yes / adjust]"

Incorporate feedback, re-present if needed.

5. Post to GitHub Issues (optional)

If user confirms and repo has GitHub remote:

gh issue create \
  --title "[PRD] <feature name>" \
  --body "$(cat <<'EOF'
[PRD content]
EOF
)" \
  --label "enhancement,ready-for-agent"

Report issue URL.

6. Save locally

Save to docs/supergraph/plans/YYYY-MM-DD-prd-<slug>.md.

7. Update CONTEXT.md

If the PRD introduced new domain terms:

# Append to CONTEXT.md
printf '\n## <term>\n[definition from PRD]\n' >> CONTEXT.md

8. Report

✅ /supergraph:prd complete
- PRD: docs/supergraph/plans/YYYY-MM-DD-prd-<slug>.md
- Issue: #N (if posted)
- Acceptance criteria: N
- Next: /supergraph:plan

Rules

  • Never skip user approval (step 4)
  • Acceptance criteria must be observable and testable — no vague criteria
  • Out of scope section is mandatory — prevents scope creep in plan
  • Post to GitHub only if user has confirmed the PRD

レビュー

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

同じリポジトリのスキル

概要と使いどころ

analyze

無料

Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.

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

datit309/supergraph222026年10月5日 更新

Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.

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

datit309/supergraph222026年10月5日 更新

caveman

無料

Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.

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

datit309/supergraph222026年10月5日 更新

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

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

datit309/supergraph222026年10月5日 更新

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

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

datit309/supergraph222026年10月5日 更新

diagnose

無料

Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.

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

datit309/supergraph222026年10月5日 更新

datit309 のスキルをすべて見る

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