Features Documents

Your agent plans from the brief you write.

Documents are pages for what's behind the work: specs, research, notes, the decisions you made. The plans your agent records land right beside them, so the why and the what live in one place, and nobody pastes context into a chat again.

Dana writes a brief in Documents, specs/sign-in, and saves it. The coding agent reads it before planning, then records its plan next to it as plans/sign-in. Dana tightens the brief to a second version, and the agent writes that into the plan as its second version. Every save is kept, with who made it.

Plan it

Plan it turns a document into tasks.

Pick the pages that are ready. Beck's own AI turns them into tasks with types, points and acceptance criteria, for a new epic or one you already have. You review every suggestion before it lands in the backlog or the icebox.

Plan it in Beck. Two documents are selected, specs/sign-in and research/auth-providers, for a new epic, Sign-in and org onboarding, in the backlog. Beck's AI suggests four tasks, each with a type, points and acceptance criteria. All four are selected, ready to add.

What Documents does.

  • Pages, in a tree.

    Paths nest the way you think: specs/sign-in, research/auth-providers. Write in markdown; it saves as you type.

  • Next to the plans.

    Plans your agent records land under plans/, and each epic's spec points back to the plan it came from.

  • Read before planning.

    Agents read the documents they need from Beck before they plan, so your brief shapes the breakdown instead of a chat message.

  • Every save is kept.

    Each version records who saved it, you or a bot. Your agent can list the versions and restore one.

  • No silent overwrites.

    If someone, or an agent, saved while you were writing, Beck stops your save and tells you, so nobody's words disappear.

  • Hand a page to an agent.

    Copy a prompt that points your agent at this workspace, and it can read and write pages with you.

Where it sits in the loop

Documents feed the Plan step and hold what Record writes: the brief goes in, and the plan comes back out next to it.

  1. 01PlanThe agent proposes the breakdown in your repo.
  2. 02Recordrecord_plan puts it in Beck as a document, epics and tasks.
  3. 03RunEach session shows up on Now while it works.
  4. 04AskQuestions come with a default, and the work goes on.
  5. 05ReviewYou accept the work, or send it back with a reason.
How the loop goes with an agent

Put the why where your agent can read it.

See plans

Free includes 50 AI credits. Recorded plans, runs and decisions use none.