specai-agent-clarification

Files (1)

• SKILL.md

SKILL.md (first lines)

# Agent clarification

## Required Skills

- `specai-bootstrap`

Use this helper only when grounded design exposes a technical constraint the codebase cannot answer. It supports grill-me; it is not a later approval gate.

### Bootstrap gate

Confirm bootstrap established the active language; if not, report the gap and do not invent or clarify requirements.

### Specification gate

Inspect the current spec and design and ground any clarification in repository evidence. If either specification or evidence is missing, report the gap; do not guess or clarify until the requirement is defined.

Confirm bootstrap has established the active language, and inspect the current spec and design. If they are missing, or repository evidence is unavailable, report the gap instead of guessing. Do not repeat business questions or facts already settled in code or design.

Look for implementation-relevant gaps in data types/nullability, limits, empty/error behavior, and concurrency. For each material gap, give repository-based context and a recommendation with concise options in the active language. Ask at most one decision per turn, following grill-me's interview rule.

Return resolved decisions and any still-open question to the controller. Resolve relevant choices in grill-me before it closes. If a gap is discovered later, reopen that clarification rather than starting planning with an unresolved requirement. Do not trigger commands or write implementation plans.

From ArceApps-dev/specai, MIT.

More from ArceApps-dev/specai