Hearing-First Skills

Gathering requirements incrementally through structured questioning prevents costly rework. This approach breaks complex tasks into major categories and actionable questions, offering concrete options to users while allowing custom input, ensuring alignment before implementation begins.

Early alignment identifies and resolves misunderstandings before development starts. Use phased questioning to systematically explore preferred branch naming, technical stack, architecture design, and functional scope, reducing project risk and improving stakeholder satisfaction.

Structure choices using concrete options rather than open-ended questions. Initiate feature development by asking users about preferred branch names and worktree directories, technical preferences like libraries and frameworks, and architecture design decisions in a phased, auditable manner.

Incremental requirement gathering with structured choices simplifies decision-making and ensures clarity. This phased approach captures user intent early, resolves ambiguities before implementation, and maintains stakeholder alignment throughout the development cycle.

Align before implementation begins to prevent costly rework and miscommunications. Use this skill when initiating a new feature, establishing branch configuration, selecting technical stack, and defining architecture—all before writing production code.