What problem does it solve? Starting development work without proper exploration and agreement leads to wasted effort, wrong assumptions, and tasks that must be redone. This Skill enforces a disciplined intake workflow so every piece of work begins with verified context, explicit owner decisions, and a properly created task, branch, and folder. ## Core Features & Use Cases - Pre-question exploration: Searches the repository, specs, rules, and past session records before asking the owner anything, so questions whose answers already exist in the tree are never asked. - Six-question grill: Structures the mandatory owner interview covering behavior changes, rule edits, task splitting, boundaries, completion criteria, and reference samples, with answers written to a grill file on disk. - Task and epic setup: Creates the product agreement via a roles pipeline, declares epics for multi-task work, and creates the task card, git branch, and task folder with plan and progress files. - Use Case: When a product owner asks for a new feature, use this Skill to explore the codebase first, ask only the unanswered questions, record the agreement, and set up the branch and task folder before writing any code. ## Quick Start Start a new task for the owner's request by exploring the repository first, then running the six-question grill and creating the task, branch, and folder.
