grill-with-docs

# Grill with docs Resolve a change's design tree with the operator while recording each answer where a fresh session can use it. Stop at a handoff-ready plan; implementation is a separate unit of work. ## Route - Use this workflow when a repository change is fuzzy but can be settled in one session. - Use `wayfinder` when the destination spans sessions, has dependent decisions that need separate research, or cannot yet become one implementation plan. - Use the ordinary plan flow when scope, language, and consequential choices are already settled. ## Establish the tree 1. Read the tracked item, existing plan/spec, `CONTEXT-MAP.md`, relevant `CONTEXT.md` files, ADRs, and the code or assets that constrain the change. Facts come from the repository; decisions come from the operator. 2. Locate the project's plan convention. Reuse an existing change plan; otherwise create one from `.harness/templates/plan.md`, `templates/plan.md`, or the same shape at `.planning/<slug>.md`, in that order of availability. 3. Map the unresolved choices as a design tree. Its **frontier** is the independent questions whose prerequisites are settled now. ## Work the frontier Ask a small numbered round from the frontier. For each question, state why it matters, the real options and trade-offs, and your recommended answer. Then wait for the operator's decisions. After each answer round: 1. Recompute the tree. Cross-check claims against the repository and surface contradictions. 2. Re...