メニュー
Use when the user wants comprehensive user-facing end-to-end test scenarios for a feature description.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Brainstorming specialist. Use before implementing any feature, fix or cli design to discuss the approach with the user first. Plans data models, storage layouts, test scenarios, and expected outputs.
Produce LOOP_<YYYY-MM-DD>_<slug>.md — a real runnable repro/verify runbook from user logs or prose. Expands to precise CLI/URL ops, builds workspace tools, runs steps 1–4 for real, records SYMPTOM CONFIRMED or VERIFY PASS. Pair with run-the-loop for fixes. Use for /establish-a-loop, "establish a loop", or "create a debug loop".
Fix until done: goal + inspect script under script/debug/, then iterate implement → inspect until PASS. Use after establish-a-loop or standalone for /run-the-loop, "loop until done", "max effort", "don't stop until".
Clarification-phase followup. Use when the user mentions followup to stay in discussion mode without moving to implementation.
OpenAI-compatible HTTP mock server for testing agents without real LLM calls. Loads a JSON config of request→response exchanges and returns pre-configured responses. Use when writing doctests or integration tests for agent runners.
Incremental deduplication workflow: map overlapping implementations, plan a PR stack into shared packages, seal doctests, migrate callers without behavior change. Use when the user mentions consolidate, dedupe, shared package, move enrichment into dot-pkgs, eliminate duplication, or /consolidate-code. Pair with investigate (overlap map) and doctest-tdd (sealed tests → impl).
| name | test-case-design-expert |
| description | Use when the user wants comprehensive user-facing end-to-end test scenarios for a feature description. |
Design user-facing end-to-end test cases for a feature. Follow these steps:
Brainstorm — Expand the feature considering core functionality, user roles, integration points, error states, and edge conditions.
Clarify — If details are ambiguous, batch all questions and call
add-pending-questions with JSON arguments. Each argument has a question
field and optional options array. After calling it, stop and wait for
answers. Only ask questions that affect test design.
Design Test Cases — For each test case, include:
Cover happy path, common edge cases, error states, and boundary conditions. Be specific and concrete.
Output to a markdown file with an auto-derived UPPER_CASE slug name (e.g.
FEATURE-TEST-DESIGN.md). The report must include the original feature
request, all clarifications and answers, the expanded feature plan, and all
test cases.
