plan

Project plan · Can change or delete · actions: get, save, agree, ask, answer, progress

For reading use plan_read, which is read-only and needs no approval: "get" here is deprecated (still works). The project's plan: a brief and roadmap you and the user agree, kept by LazyFrog so later sessions, other AIs and collaborators start from it (the user sees it on the Plan tab and on the chat's card). Optional; it is advice, never a gate. Free-form Markdown in content, in whatever shape suits the project ("- [ ] …" / "- [x] …" lines show as milestones), plus an optional structured core (brief, audience, size, mustHaves, later, data, integrations, intake, content, look, doneWhen, estimate). intake: for anything it takes in from people (a form, sign-up, booking, order, upload), what happens next: keptIn, notify (who is told, how quickly), senderSees, keptFor. content: the content inventory, per page: items (what, source, permission, note) and missing; discover it before design for a business with no site to capture. action "get": read it. "save": content and/or core (the core fields you pass replace those; content is also written to PLAN.md); pass base: the revision from your last get, so an edit the user made on the Plan tab isn't overwritten unseen; written_by_user: true when the plan is the user's own (their PRD). "ask": the round's open questions (questions: at most 5 open at a time, each with 2-6 options and a default among them); the card shows them as buttons. The look is one of them, not a second round: propose the directions first (look propose), then include a question with kind: "look" whose options are their names and whose default is your recommendation (the card shows swatches, the Plan tab previews); answering it chooses the look. "answer": record the user's answers (answers: [{id, answer}], or defaults: true for every open question). "agree": the user said yes to the plan as it stands, after seeing it (recorded with a fingerprint): only they can agree, so pass said, their own words, and wait for their reply first (an agree in the same turn as the save is refused); with defaults: true, "just build it" (or their request already said exactly what to build): recorded as building with the defaults, not as an agreement. "progress": tick or untick done-when items (tick / untick: numbers from 1, or the items' text). Ticking never undoes the user's agreement; changing the must-haves, data or integrations asks for it again. A plan lives in a project: new projects start in planning. Follow the user: if they want to just build, build.