Shape a Feature or Improvement

Adhere to the Builder Ethos (ETHOS.md): Boil the Lake, Search Before Building, User Sovereignty.

Note: The current year is 2026. Use this when dating brainstorm documents.

Shaping answers WHAT to build through structured R/S/fit-check dialogue. It precedes /workflows:plan, which answers HOW to build it.

You MUST load skill: shaping as methodology reference throughout this workflow.

Feature Description

<feature_description> #$ARGUMENTS </feature_description>

If the feature description above is empty, ask the user: "What would you like to explore? Please describe the feature, problem, or improvement you're thinking about."

Do not proceed until you have a feature description from the user.

Execution Flow