Create a design project. It starts in the 'discovery' phase: problem, users and goal are required. Mode 'strict' (default) blocks advancing until each phase is complete; 'free' allows advancing and reports what was skipped.

List projects with their id, name, phase and status. Use it to find a projectId.

Change a requirement's title, description or priority. Only the fields you pass are changed.

Delete a requirement. It is also removed from the requirementIds of any user story that covered it.

Delete a user story.

Mark one acceptance criterion of a user story as done or not done. The index is 0-based, in the order of the criteria.

Archive or unarchive a project. Archived projects are hidden from list_projects by default. Nothing is deleted.

Change a project's mode: 'strict' or 'free'. Applies from the next phase change.

Change a project's name, problem, users or goal. Only the fields you pass are changed.

Search requirements and user stories by text (case-insensitive). Optionally limit to one project.

Create a new project from an existing one, copying its requirements and user stories as open items. Useful as a template for a new client or product. Statuses and RICE scores are not copied.

Import requirements and user stories from CSV text, in the format produced by export_backlog. Requirement rows need type and title; story rows need persona, goal, benefit and criteria (separated by ' | '). Story-to-requirement links are not restored.

Bind a project to its work tracker: jira (with a Jira project key, e.g. PROJ) or github (with owner/repo). Set it once, before sending anything. A project with items already sent cannot change tracker.

Create the project's work items in its tracker: one Task per requirement and one Story per user story. Items already sent are skipped. With update: true, refreshes the items already linked. dryRun (default true) only lists what would be sent. Set the tracker first with set_project_tracker.

Read the status of the project's linked items in its tracker and mark them done or open in Yeti. Read-only on the tracker.

Summarise a project's progress: requirements by priority and status, story coverage of musts, acceptance criteria done, RICE leader, Jira links and what is missing to close.

List user stories, optionally for one project, with their ids, criteria state and Jira key. Use it to find a storyId.

Permanently delete a project with its requirements and user stories. Requires confirm: true. This cannot be undone; issues already created in Jira are not touched.

Change a user story's persona, goal, benefit, linked requirements or acceptance criteria. Only the fields you pass change. Changing the criteria resets their done state.

List the flow diagrams saved in a project, with their index. Use the index to refer to a diagram.

Delete one saved flow diagram from a project, by the index shown by list_flows.

Write a read-only HTML dashboard to data/exports/dashboard.html: phases, what is missing, musts covered by stories, RICE scores and flow diagrams. Open the file in a browser.

Start the local, read-only Yeti dashboard and return its address (http://127.0.0.1:...). It shows phases, what is missing, musts and their stories, RICE and flows, and refreshes by itself. It runs on this computer only, while Yeti runs.

Record a design decision for a project: what was chosen, why, and which alternatives were rejected. Decisions are kept with the project, so the reasons outlive the chat.

List the design decisions recorded for a project, oldest first.

List the starter project templates: a marketplace MVP and a customer self-service portal. Use one with create_project_from_template.

Create a project from a starter template. It starts in discovery with its requirements and user stories open, linked to each other. Adapt them afterwards with the usual tools.

Show a project's status: current phase, what is missing to advance, and linked items.

Move to the next phase. In 'strict' mode, it lists what is missing and does not advance. In 'free' mode, it advances and reports what was skipped. After 'verification' it closes the project.

Record a product requirement with a MoSCoW priority (must, should, could, wont).

List requirements, optionally filtered by priority, status and project. Most important first.

Mark a requirement as open or done.

Create a user story in the format 'As a I want so that ', with acceptance criteria.

Compute RICE scores (Reach × Impact × Confidence ÷ Effort) for a list of ideas and sort them. With projectId, saves the result to the project.

Generate a Mermaid flowchart from a list of steps. Steps are linked in order; a decision (diamond) gets a 'Yes' edge to the next step, or to 'yes' if set, and a 'No' edge to 'no' if set. With projectId, saves the diagram to the project.

Export a project backlog as Markdown or CSV: requirements (most important first) and user stories.