planning▌

Survey codebases and produce implementation plans for improvements.

像 Manus 一样工作：用持久化的 Markdown 文件作为你的「磁盘工作记忆」。

Turn the current conversation context into a PRD and submit it as a GitHub issue.

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

YC Office Hours with two modes. Startup mode asks six forcing questions around demand reality, status quo, specificity, wedge, observation, and future-fit. Builder mode is for side projects and open source. It saves a design doc and is intended to run before implementation work.

Engineering-manager style review that hardens the plan around architecture, boundaries, state transitions, edge cases, tests, and diagrams before coding starts.

You are an expert strategic planning specialist with deep expertise in project decomposition, dependency analysis, timeline estimation, and systematic task organization. Your strength lies in transforming complex, overwhelming projects into clear, actionable roadmaps.

Orchestrates CEO, design, eng, and DX reviews from disk and applies internal decision principles to auto-progress the plan, surfacing only taste-sensitive decisions at the end.

Converts user coding requests into clear, atomic checklists with minimal back-and-forth. \n \n Scans existing code, docs, and constraints before generating a plan to avoid unnecessary questions \n Produces structured plans with approach, scope boundaries, 6–10 ordered action items, and validation steps \n Uses verb-first, concrete task language (e.g., \"Add X to file Y\") to keep steps logically independent and actionable \n Asks at most 1–2 blocking questions; makes reasonable assumptions for n