원클릭으로 Manus에서 모든 스킬 실행

시작하기

boring-loop-grill

스타45

포크2

업데이트2026년 7월 20일 08:37

Use for /loop-grill: clarify one Kanzen issue with grill-me and ask-user, then return it to triage or keep it blocked.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

hachej

hachej/boring-ui

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Boring Loop Grill

Make an unclear issue clear enough to route. Do not plan deeply. Do not implement.

Steps

Read the issue, comments, captured context, screenshots, and nearest code/docs.
Self-answer anything the repo can answer quickly.
Ask only questions that change routing, acceptance, proof, or risk.
Use grill-me style questions; use ask-user for async owner input.
Write the clarified summary, acceptance, proof path, and open risks back to the issue.

Exit

Still unclear: state:blocked phase:grill track:owner, gate clarity.
Clear enough: state:queued phase:triage track:owner, gate triage.
Not worth doing: state:done, with a short reason.

For async grill, leave one pending ask-user session with issue URL/title, why it is blocked, the questions, answer format, and resume command /loop-grill <issue>.

이 저장소의 다른 Skills

같은 저장소

exec

hachej/boring-ui

Drive one ready artifact through implementation, proof, review, and owner handoff.

2026-07-2045

hachej/boring-ui

Review the named UI scenario or emit one bounded improvement packet.

2026-07-2045

boring-google-signup-setup

hachej/boring-ui

Teach a boring-ui child app how to enable Google signup with @hachej/boring-core. Use when the user asks for Google auth, Google OAuth, social signup, or how to turn on Google sign-in/sign-up in a child app.

2026-07-2045

ask-boring

hachej/boring-ui

Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.

2026-07-2045

code-review-thermo

hachej/boring-ui

Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.

2026-07-2045

ask-boring

hachej/boring-ui

Route a request to the right Boring v2 workflow skill without doing the work.

2026-07-2045

name	boring-loop-grill
description	Use for /loop-grill: clarify one Kanzen issue with grill-me and ask-user, then return it to triage or keep it blocked.

Boring Loop Grill

Make an unclear issue clear enough to route. Do not plan deeply. Do not implement.

Steps

Read the issue, comments, captured context, screenshots, and nearest code/docs.
Self-answer anything the repo can answer quickly.
Ask only questions that change routing, acceptance, proof, or risk.
Use grill-me style questions; use ask-user for async owner input.
Write the clarified summary, acceptance, proof path, and open risks back to the issue.

Exit

Still unclear: state:blocked phase:grill track:owner, gate clarity.
Clear enough: state:queued phase:triage track:owner, gate triage.
Not worth doing: state:done, with a short reason.

For async grill, leave one pending ask-user session with issue URL/title, why it is blocked, the questions, answer format, and resume command /loop-grill <issue>.