story-new

Story New

Create a new story from an idea. Stories can be quick sparks (just the idea), creatively explored, or fully designed — you choose how deep to go.

Flow

Step 1: Capture the Idea

"What's the story about?"

[User describes the idea]

CRITICAL: Questions vs Answers

Before capturing ANYTHING, distinguish:

• Question from user: "What do you recommend?" / "What should this do?" / "Any ideas?" → ANSWER THE QUESTION FIRST. Provide recommendations/options. Do NOT capture or lock anything. Wait for user to explicitly confirm.
• Answer from user: "Let's do X" / "The spark is Y" / "It should handle Z" → This is input to capture.

Never lock or save based on a question. Questions require answers, not actions.

Step 2: Clarify (if needed)

If the idea is vague or could mean multiple things, use AskUserQuestion to clarify.

For UI/layout changes:

question: "What aspect do you want to change?"
header: "Focus"
options:
  - label: "Rearrange sections"
    description: "Move things around, change order"
  - label: "Responsive behavior"
    description: "How it works on different screen sizes"
  - label: "Add/remove elements"
    description: "New components or removing existing ones"
  - label: "Overall structure"
    description: "Sidebar vs stacked, major layout shift"

For feature work:

question: "What's the core of this change?"
header: "Focus"
options:
  - label: "New functionality"
    description: "Something that doesn't exist yet"
  - label: "Improve existing"
    description: "Make current feature better"
  - label: "Fix a problem"
    description: "Something's broken or confusing"
  - label: "Performance/technical"
    description: "Speed, reliability, code quality"

If user provides custom text: Use their clarification and proceed to Step 2.5.

If idea is already clear: Skip directly to Step 2.5.

Step 2.5: Story Source Detection

Before asking "How deep do you want to go?" (Step 3), check whether this project has planning docs OR converged mockups that the story could be built from.