harness-grill

Interviews users one question at a time to produce an aligned requirement brief.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-grill-alan-ift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-grill
Source: https://github.com/Alan-IFT/harness-kit/tree/main/skills/harness-grill
Command: npx skills add https://github.com/Alan-IFT/harness-kit --skill harness-grill-alan-ift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or ambiguous requirements cause AI pipelines to build the wrong thing. This Skill runs a structured pre-pipeline interview that forces ambiguities into the open before any design or code is written, ending with an aligned brief the downstream pipeline can consume. ## Core Features & Use Cases - One-question-at-a-time interview: Asks exactly one open question per turn, each with a recommended answer the user can accept, override, or refine. - Codebase self-answering: Explores the repository to resolve questions the code already answers (conventions, prior art, file locations) instead of asking the user. - Aligned brief output: Writes the agreed decisions and residual open items to docs/features/<slug>/INPUT.md for /harness, /harness-plan, or /harness-stream to consume, with overwrite confirmation on collisions. - Use Case: You have a fuzzy feature idea and suspect the agent would build something subtly off. Run the grill session, answer the questions, and hand the resulting brief to the full pipeline. ## Quick Start Ask the agent to grill you on your feature idea before running the pipeline, then answer each question one at a time until the aligned brief is written.

Frequently Asked Questions about harness-grill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify a vague feature requirement before coding?▼

Run a grill session that interviews you one question at a time, each with a recommended answer. It self-answers questions the codebase already resolves, then writes an aligned brief to docs/features/<slug>/INPUT.md for the pipeline to consume.

What is the difference between harness-grill and harness-plan?▼

harness-grill discovers the requirement through an interview before any design exists, while harness-plan vets an existing design without writing code. Grill precedes the pipeline; plan runs the design stages of it.

Does harness-grill write code or run the development pipeline?▼

No. It only produces an aligned brief at docs/features/<slug>/INPUT.md and stops. It never runs the pipeline, writes design or code, or produces research findings.

What happens if I end the interview before alignment is complete?▼

The Skill writes whatever was agreed so far and records the residual open items in the brief. Partial interview results are never silently lost.

Is CONTEXT.md required for the requirement interview to work?▼

No. CONTEXT.md is a soft dependency: if present, its glossary terms are used in questions and the brief; if absent, the interview proceeds normally without blocking or creating the file.