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

pitch-packager

Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

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

Pitch packager

Reviewers start with the same unknowns the builder started with, plus one more: whether the builder accounted for the failure points an expert would probe. A good pitch doc kills both in one read.

Steps

  1. Collect the artifacts: the spec or plan, the prototype or demo, the implementation notes, and the diff. Ask for a demo recording or screenshots if any user-facing behavior changed — lead with that.
  2. Structure the document in reading order for a skeptic:
    • The demo — what it looks like working, first. A GIF or screenshot beats prose.
    • The problem and the bet — two paragraphs max: what this solves and the approach chosen over the alternatives.
    • What an expert would ask — the 3-5 hard questions a reviewer in this domain would raise (edge cases, scale, failure modes, migration), each answered honestly, including "not handled, here's why that's acceptable for now."
    • Deviations from plan — lifted straight from implementation-notes, because surprises found in review cost trust.
    • What's NOT in this change — scope fences, so the review doesn't sprawl.
  3. Keep it one page. Link out to the spec, notes, and diff rather than inlining them.
  4. Match the medium to the venue: a Slack-pasteable doc, a PR description, or a standalone HTML page — ask which if unclear.

Guardrails

  • Never oversell: a pitch that hides a known weakness converts one approval into a permanent credibility loss.
  • The "what an expert would ask" section is the heart. If it's easy to write, the questions aren't hard enough.
  • If the work isn't actually ready, the honest pitch is a status update, and saying so is part of this skill.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

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

Neeeophytee/finding-unknowns-skills3472026年9月28日 更新

Neeeophytee のスキルをすべて見る

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