메뉴
This skill should be used when users request new features, improvements, fixes, or ask to create plans. It facilitates BDD planning by asking clarifying questions and producing a clean, tracker-agnostic plan with acceptance criteria.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Draft or edit public documentation, product, UI or CLI copy, external drafts, or explicitly requested editorial reviews in clear, plain British English. Do not use for ordinary chat, commentary, status, plans, code-only work, research, internal reviews, worker prompts or evidence gathering.
Use only when the user explicitly invokes $grill-me or asks to be grilled, pressure-tested, challenged, interrogated, questioned first, or aligned before work starts. Broad task-alignment workflow for software, research, writing, planning, purchasing, operations, design, and other generic tasks. Do not invoke proactively; if a task seems underspecified, suggest that the user can invoke this skill without entering the workflow.
Maintain and update fast-moving AI tools in the Nix workspace. Use when asked to refresh, verify, package, install, apply, or compare current versions of Codex, Claude, pi, MCP tools, XcodeBuildMCP, markit/markitdown, qmd, spogo, or other AI developer tools managed through nix-ai-tools, nixos-config, Homebrew tap locks, or ai-stack.
Use summarize.sh to summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files. Use for markdownified YouTube transcripts with summarize --extract --format md --markdown-mode llm.
High-quality YouTube transcription from audio using yt-dlp + whisper.cpp through the local summarize CLI. Use when captions are unavailable/untrusted or the user explicitly wants audio transcription. For summarize.sh markdownified YouTube transcripts, use the summarize skill instead.
Write durable Codex session goals. Use when the user asks to write, improve, set, update, or replace a session goal; says the current session goal is too vague, too narrow, too specific, or slop; asks for a long-running/autonomous objective to be framed as a goal; or asks Codex to encode vision, north star, current slice, success criteria, deliverable, CTO briefing, alignment needs, review loop, and completion proof into a session goal. Do not use for ordinary planning, CTO briefs, reviews, or research unless the user asks to create or revise a session goal.
| name | product-manager |
| description | This skill should be used when users request new features, improvements, fixes, or ask to create plans. It facilitates BDD planning by asking clarifying questions and producing a clean, tracker-agnostic plan with acceptance criteria. |
You turn vague requests into a clear plan with acceptance criteria. You do not assume a specific issue tracker. If a tracker exists, ask which system to use and follow the repo’s conventions.
Use this skill when the user says things like:
Ask only what is required to unblock a plan:
If answers are already present, do not ask.
Produce:
Format acceptance criteria as:
If the repo has a tracker:
Recommendation
Key Tradeoffs
Plan
Acceptance Criteria
Risks / Unknowns
Decision Needed (only if required)
