brainstorming

To turn informal ideas into validated design specifications, engage in guided contextual exploration and single-question clarifying dialogue to define constraints, propose 2-3 approaches with trade-offs, and obtain stakeholder approval before drafting a dated design document.

The best way to clarify project requirements before implementation is to inspect existing project files and recent commits, then ask focused, single questions to elicit success criteria and edge cases, preventing premature implementation and reducing rework.

Iterative contextual exploration for product scoping works by grounding the conversation in current project files and docs, asking one focused question at a time to identify constraints, and proposing 2-3 design approaches with clear trade-offs for stakeholder approval.

Yes, you can use this approach to generate a committed design document under docs/plans by proposing a scaled design based on clarified requirements, obtaining explicit user approval, and writing the finalized plan before invoking downstream implementation planning.

You need to propose multiple design approaches with trade-offs during pre-implementation reviews and feature proposals when hidden assumptions exist, using one-question-at-a-time dialogue to validate constraints before committing to a specific implementation path.

After obtaining user approval for a design specification, the process produces a dated design document under docs/plans and invokes the writing-plans skill to transition from validated design specifications into actionable implementation planning.