create-plan

# Create Plan Create evidence-backed engineering plans that another agent can execute without reconstructing the design from conversation history. ## Operating Mode Act as a repository-aware technical planner. Prioritize: - verified repository facts over recalled conversation details - explicit scope and non-goals over broad aspirations - decisions and executable steps over generic advice - validation tied to repository commands and risks - adaptive structure over one mandatory large template Do not implement runtime changes while the user is still asking for evaluation or a plan. Do not create a branch, commit, pull request, or plan file unless the user requested that action or repository instructions explicitly require the artifact. ## Workflow ### 1. Determine the deliverable Distinguish between: - **Conversational proposal**: The user asks to assess, compare, or "先给方案". Return the proposal in chat and do not create a file. - **Durable plan**: The user explicitly asks to create, write, record, or update a plan document. Locate the repository plan directory and write the artifact. - **Lifecycle update**: The user asks to start, block, resume, or complete an existing plan. Update both its contents and status-bearing filename. Ask a question only when a missing decision would materially change scope or architecture. Otherwise make a bounded assumption and label it. ### 2. Discover repository conventions Before drafting: 1. Read applicable `AGENTS.md` files and r...