specai-grill-me

Files (1)

• SKILL.md

SKILL.md (first lines)

# Grill-me

## Required Skills

- `specai-bootstrap`

Ground the request in the repository, then ask one design question at a time until no relevant design, implementation, or technology choice remains unresolved. Do not leave grill-me with an open decision that could change scope, behavior, architecture, or technology.

### Gate G1

Before exit, record grounding evidence and settle all relevant decisions; do not exit with an open decision.

## Ground first

Identify domain terms, inspect relevant code/configuration/APIs, and record the searched terms, inspected sources, and facts. Before asking anything, check whether the repository can answer it. If repository inspection is unavailable, report the blocker; do not guess.

## Interview

- Ask exactly one unresolved user decision per turn, with only the repository facts needed for context.
- Keep business behavior, data/state, integrations, security, UX, constraints, and edge cases in view.
- Probe vague answers and explain material trade-offs. Do not ask about facts the codebase establishes.
- Business and product decisions belong here; technical details already settled by the approved design do not.

Before each turn, make sure it contains one decision question. When none remain, stop asking and return a concise record of agreed behavior, decisions, constraints, and remaining non-decision notes. Do not start planning until all relevant choices are resolved.

### Gate G2 — Response check

Each response that asks the user a question must contain exactly one focused, unresolved decision question. When none remain, ask no question and return the concise decision record.

Do not generate code during the interview. Load domain modeling only when a domain term or durable architectural trade-off needs recording; use the PRD/planning skills for their phases.

From ArceApps-dev/specai, MIT.

More from ArceApps-dev/specai