brainstorming

To define product requirements, explore project context like files and recent commits, then ask clarifying questions one at a time to refine purpose, constraints, and success criteria before producing an approved design plan.

Evaluating trade-offs for component design involves presenting 2–3 approaches with a recommended direction. This allows you to compare options and select an approved path forward before writing a specification document.

Writing an approved specification for behavioral changes requires an approval-gated design presentation. After proposing approaches and receiving user approval, the validated spec is committed to a dedicated project specs directory.

Yes, you can visualize mockups during product planning using a browser-based Visual Companion. This optional tool provides visual support for mockups and diagrams when the design topic is meaningfully visual.

User approval for spec writing is needed before implementation begins and before handing off to a planning skill. A hard review gate blocks code changes until the design spec is explicitly reviewed and approved by the user.

Refining scope for ambiguous engineering intent starts with a context exploration step to ground the design in current reality. A guided questioning loop clarifies the requested work when it could be implemented in multiple ways.