loop-me
無料Grill me about specs for the workflows I want to build, within this workspace.
日本語の概要は準備中です。原文の説明を表示しています。
222 件 ・ 関連度順
概要と使いどころ
Grill me about specs for the workflows I want to build, within this workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design.
日本語の概要は準備中です。原文の説明を表示しています。
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
日本語の概要は準備中です。原文の説明を表示しています。
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
日本語の概要は準備中です。原文の説明を表示しています。
Email triage system that handles both one-time setup and recurring triage in a single skill. Auto-detects state: if no knowledge base exists at ${WORKSPACE}/Email/, runs an 8-section onboarding interview (grill-me discipline, one question at a time) to build a 7-file personalized KB, then offers to run triage immediately. If the KB already exists, skips setup and goes straight to triage — searches recent emails, classifies them via the user's taxonomy, researches new senders, generates TAKE IT/WORTH/PASS/FLAG recommendations, drafts replies (NEVER sends), delivers a report, and updates the KB. Use with 'update' argument to refresh preferences. Setup triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management'. Triage triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when user ask to "interview me".
日本語の概要は準備中です。原文の説明を表示しています。
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify research intent and produce draft readiness for human exit.
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
日本語の概要は準備中です。原文の説明を表示しています。
The fifteen fundamental cooking techniques that together cover most home kitchen work. Organized by the transformation they perform (heat transfer, water management, emulsion, ferment, cut) rather than by cuisine. Covers knife work, sauté, sear, braise, roast, poach, boil, steam, grill, bake, stew, reduce, deglaze, emulsify, and pickle/ferment, each with the physics, the signal, the common failure, and a diagnostic question. Use when teaching a cook, substituting a technique, or diagnosing why a dish failed.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain a one-page burn-down spec as the working memory of a large or multi-session task. Use when work spans sessions, when the user asks for a spec or brief, or when a grill ends on a task too big to carry in a confirmed summary alone.
日本語の概要は準備中です。原文の説明を表示しています。
Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.
日本語の概要は準備中です。原文の説明を表示しています。
Edit Specification: Use when the user wants to "edit" the SpecBook-based specification (SPEC) in one shot from a query, with optional grilling, SpecBook validation, looping, and Git worktree isolation.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a design needs pressure-testing for UX, information architecture, states, and accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an engineering plan needs pressure-testing for architecture, complexity, data, risk, and operability.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product idea needs pressure-testing against alternatives, category, urgency, and distribution.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Brain /brain-brief: after intake, research, and grill have enough signal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository decision needs an interview plus durable terminology and decision records. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to optimize code, make a path faster, make this as fast as possible, reduce allocations, repair a regression, profile a target, grill every inefficiency, or run a subsystem or repo-wide performance campaign against a measured floor; when a performance requirement, slowness report, Core Web Vitals miss, or profiling evidence identifies a bottleneck; or for an "extremely optimize" performance campaign, optimizing suspected hot paths without waiting for benchmarks, or estimating hot and complexity-neutral cold paths while refusing complexity theater. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。