メニュー
Use when adding or changing a capability surface such as a public function, API, command, prompt, workflow, schema/helper, policy, or reusable instruction.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a request needs product/design exploration, unclear requirements, multiple viable approaches, UI/UX choices, or new behavior whose intent is not yet bounded.
Use when 2+ independent tasks, failures, research lanes, exploration lanes, or path-scoped investigations can run without shared state, shared files, or sequential dependency.
Use when executing a written implementation plan inline in the current session with checkpoints and verification.
Use when implementation is complete, verification passes, and the remaining decision is how to integrate, merge, PR, clean up, or finish the branch.
Use when creating or revising docs, plans, records, PR text, handoffs, or other prose that should be sparse, direct, and low-context.
Use when changing prompt templates, AGENTS.md, CLAUDE.md, MCP/tool instructions, skills, governance docs, or any instruction surface where verbosity, duplicated doctrine, hidden exemptions, unclear provenance, or weak enforcement could affect agent behavior.
| name | existing-capability-first |
| description | Use when adding or changing a capability surface such as a public function, API, command, prompt, workflow, schema/helper, policy, or reusable instruction. |
Search before inventing. Reuse, extend, replace, or delete existing capability before adding another home for the same concept.
Purpose: keep systems coherent instead of accumulating parallel surfaces. Consumer: agents adding or changing reusable behavior, APIs, commands, prompts, workflows, policies, schemas, or helpers. Failure consequence: duplicate capability diverges; callers pick different paths; old bugs survive because the new surface bypasses rather than fixes them. Falsifier: the change is pure formatting, pure refactor, or test-only work that does not alter a contract or add a reusable surface.
Use when a diff adds or changes:
Skip when no behavior or contract surface changes.
Search in this order, using repository-native tools first:
Record search keys and nearest artifact. If none exists, say none plus the
reason existing surfaces cannot satisfy the PDD contract.
Do not stop at shallow name search in large repos. Search by failure class, consumer, and data shape too.
