메뉴
This skill should only be used when the user uses the word workflow and asks to develop or implement changes with a verification-first loop and clean handoff/pickup boundaries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
Calibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with standard unit tests).
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
This skill should be used when shaping a software change and needing to breadboard the solution at the right level of abstraction (places, affordances, connections), including mapping an existing system via UI + code affordances, producing a wiring diagram, a parts/BOM plan, a fit check, and (when relevant) an extract-vs-duplicate analysis.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
This skill should be used when a user needs a demo package that starts with a live demo (not slides) and produces both a demo script and a navigable single-file HTML runbook, including caveats, respectful competitive comparison, and LLM architecture details (RAG, evals, observability).
| name | wf-develop |
| description | This skill should only be used when the user uses the word workflow and asks to develop or implement changes with a verification-first loop and clean handoff/pickup boundaries. |
Implement changes with a verification-first loop, keeping context clean between workflow steps.
prd.json (single-PRD dossier or slice PRD).
plan.md may exist for higher-risk work, but it’s optional.
Prefer plan-driven work when plan.md exists, but allow PRD-driven work (especially with PRD JSON: prd.json).
Preferred:
prd.json ) - implement one prd.json at a time.prd.json / prds/<slice_id>_<slug>/prd.json)Optional:
plan.md path (only when created by wf-plan)Also:
passes and notes to reflect reality (prd.json or a slice prds/.../prd.json)pickup skill if:
prd.json): check if prd.md exists. If yes, run create-json-prd first (NO-GO if schema invalid). If not, ask user to create prd.md.plan.md exists: use it in conjunction with prd.json to guide development.prd.json directly (this is normal for small work).passes=true for stories fully meeting criterianotes for partials, tradeoffs, follow-upshandoff/new then pickup with the handoff note pathcompound-docs skillsprd.json or slice prds/.../prd.json).