[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When working with claude code, it commonly asks if I want to do one thing or another without an easy way to respond. I would prefer to be asked yes or no questions ( Do you want to do this? ) or be given a list of options ( Do you want to do A, B, or C ) . This default behavior is very unintuitive and difficult to work with. For example, Claude asked "Want me to start on the Foundation milestone, or would you prefer to scope it first?" How does one respond to this question efficiently? Do I respond with milestone, or Foundation, or scope, or first option, or second option?

Proposed Solution

It would be so much more efficient if it queried "Want me to start on the Foundation milestone (A), or would you prefer to scope it first (B), or something else (C)?" Thank you for your excellent work and dedication to safety and the survival of the human race :) .

Alternative Solutions

I need to teach the agent how to do this in every instance and have it remember.
❯ Don't give me 2 options without a easy response. Either give me a yes or no query or give me numbered options. Remember this.

● Got it — yes/no or numbered options, never two options without an easy response. Let me save this.

Read 1 file, wrote 2 memories (ctrl+o to expand)

● Saved. I'll present choices that way from now on.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

I've read the README — *** is bootstrapped with specs in place but no implementation yet. The specs are the source of truth, and the
build sequence is Foundation → Core API → Search/AI → Block Editor → Knowledge Graph → Migration.

What would you like to do? A few natural starting points:

• Kick off Milestone 1 (Foundation) — scaffold the FastAPI app, Docker Compose stack (Postgres+pgvector, MinIO), uv project,

SQLAlchemy/Alembic setup, per the spec's E12 Phase 1. This would be branch m01-foundation off main.

• Review the specs together first — walk through _SPEC.md / _SPEC_EXECUTION.md to confirm the Foundation milestone's scope

before writing code.

• Something else — a specific question, a scope decision, or a different part of the build.

Want me to start on the Foundation milestone, or would you prefer to scope it first?

✻ Crunched for 7s

❯ Don't give me 2 options without an easy response. Either give me a yes or no query or give me numbered options. Remember this.

● Got it — yes/no or numbered options, never two options without an easy response. Let me save this.

Read 1 file, wrote 2 memories (ctrl+o to expand)

● Saved. I'll present choices that way from now on.

Back to *** — shall I start on Milestone 1 (Foundation: uv project, FastAPI app, Docker Compose with Postgres+pgvector and MinIO,
SQLAlchemy/Alembic), on branch m01-foundation?

Additional Context

_No response_