grill-me

To define project scope before implementation, you can use a structured interview process that asks one question at a time to surface critical decisions, provides default recommendations, and persists those decisions to a run folder for durable logging.

Running a project kickoff interview for ambiguous design tasks works best by prompting one question at a time, leveraging file-inspection to inform questions from existing project context, and recording decisions to minimize unnecessary prompts and reduce ambiguity.

Yes, you can use an interview-based approach to capture requirements for greenfield projects, as it applies to greenfield work, feature development, and ambiguous tasks by guiding teams through a controlled sequence of questions with durable decision logging.

To persist project decisions for auditability and handoff, the interview process records all decisions in a decisions.md file located within the specific run folder at .agent-runs/<run-id>/, ensuring durable logging and traceability.

Yes, you need a current run folder to start interviewing users for project scope, because the process requires an active run directory to persist decisions and support inspecting existing files to inform the interview questions.

Asking one question at a time during the interview surfaces critical decisions in a controlled sequence, preventing user overwhelm and allowing file-inspection to inform subsequent questions, which accelerates decision making with concise rationales.