Take stock

This journey helps you get your bearings: where the project stands, what awaits a decision from you, what happened in the last sessions. You come here at the start of a working session, or when you no longer know where you are.

What you ask the agent

💬 You ask your agent

« Where does the project stand? »

→ The agent callseffortless_status

💬 You ask your agent

« What is waiting for me? »

→ The agent callseffortless_attention

💬 You ask your agent

« Show me the tree of epics and stories. »

→ The agent callseffortless_project_tree

💬 You ask your agent

« What did we do in the last sessions? »

→ The agent callseffortless_sessions

💬 You ask your agent

« Record this summary of the session: CSV export finished, tests to write. »

→ The agent callseffortless_session_summary

• summary = CSV export finished, tests to write

💬 You ask your agent

« Update my Kessho memory with the project's state. »

→ The agent callseffortless_secondbrain_sync

💬 You ask your agent

« Which modules does the project declare, and what is their git state? »

→ The agent callseffortless_modules

💬 You ask your agent

« Which work mode are we in? Switch to semi-auto. »

→ The agent callseffortless_mode_show

💬 You ask your agent

« Which features does the agent have available? »

→ The agent callseffortless_features

What the agent does

Read the state

1. effortless_status returns the full status: phases, active epic and story, backlog.
2. effortless_attention returns what awaits you: the work in progress, the open points (questions, recipes to verify, orphan tasks, critical anomalies, git, delivery, drift), the statistics and the queue. An unreadable source is named in skipped.
3. effortless_project_tree returns the whole tree: epics, stories, statuses.

These three verbs read; they write nothing.

See the modules

effortless_modules lists the declared modules: identity (path, languages, model, standards), git state and version, delivery, and the work cited by the commits of their path over 90 days. effortless_widget_list lists the dashboard's custom widgets. Both are read-only.

Pick up the sessions

1. effortless_sessions returns the history, most recent first: the Kessho memory first, otherwise the local sessions of the machine. last gives the latest (title, summary); the reason for a fallback is in skipped.
2. effortless_session_summary writes the summary of the current session into .effortless/sessions/, local to your machine. Parameter: summary.
3. effortless_secondbrain_sync archives the project's state (OPALE phase, decisions and tasks of the active story) into your Kessho memory, through Kessho's own server: Effortless never writes into the vault. It writes an archive only if the state changed since the last one; otherwise it answers "up to date". The Kessho project is found by its repository. If it does not exist, the kessho:projetAbsent refusal says so: with your consent, the agent calls the verb again with create: true, which creates it. The context you keep in Kessho is never modified.
4. Every closed story and epic is also archived in Kessho on its own. Without Kessho, closing still works: its answer says why nothing was archived.

Set the mode

effortless_mode_show gives the current mode with its description. effortless_mode_set changes it (full, semi-auto or tutore) and writes it to effortless.json. What each mode allows: see With an agent.

List what Effortless can do

effortless_features lists the verb registry. With write_doc: true, it regenerates docs/FEATURES.md and refreshes the derived section of AGENTS.md and the import in CLAUDE.md. Without that parameter, nothing is written.

What you get

• An answer from the agent that names the active epic and story, what is waiting, and the next useful step.
• A session file in .effortless/sessions/ after effortless_session_summary.
• An updated work mode in effortless.json.
• On screen: the Dashboard is the resume screen (in progress, open points, git, statistics); the Backlog shows the tree and the session history; the Modules screen shows the modules; the mode is set in Project settings.

When the agent is refused

Situation	What the refusal says	What to do
A project verb is called outside a project	mcp:racineProjetIntrouvable	Set EFFORTLESS_PROJECT if the project exists elsewhere; otherwise effortless_init creates one.
effortless_session_summary with an empty summary	sessions:summaryEmpty	Pass summary: what the session did and observed, in a few sentences.
effortless_mode_set with an unknown mode	"Invalid mode" message, no code; nothing is written	Pass full, semi-auto or tutore.
effortless_features with write_doc: true on a file that is not writable	guide:writeFailed	Make the named file writable, then call again with write_doc: true.

effortless_status and effortless_features also work before any project exists.