Skip to content
Documentation
Skill

/brief

Read the current Space-owned project Brief from Wenlan for Codex. With an optional topic, appends separately labeled related context from the same Space. Invoked as /brief [topic] when resuming work or asking to catch up.

From plugin
wenlan
6415 skills3 agents1 MCP
Install
$ npx -y skills add 7xuanlu/wenlan --skill brief --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/brief

Context preview

The summary Claude sees to decide when to auto-load this skill.

Read the current Space-owned project Brief from Wenlan for Codex. With an optional topic, appends separately labeled related context from the same Space. Invoked as /brief [topic] when resuming work or asking to catch up.

SKILL.md

brief.SKILL.md
name: brief
description: >
  Read the current Space-owned project Brief from Wenlan for Codex. With an
  optional topic, appends separately labeled related context from the same
  Space. Invoked as /brief [topic] when resuming work or asking to catch up.
argument-hint: "[topic]"
allowed-tools: ["Bash", "mcp__wenlan__brief", "mcp__wenlan__list_pending_revisions", "mcp__wenlan__accept_revision", "mcp__wenlan__dismiss_revision"]
user-invocable: true

/brief

Read one Space's current project snapshot. The daemon Brief is authoritative; `~/.wenlan/sessions/_status/*.md` is only a one-way human-readable receipt and must never be read as product state.

1. Resolve the Space

raw_args="<the full argument string passed to /brief>"
space_arg="$(printf '%s\n' "$raw_args" | grep -oE 'space:[A-Za-z0-9_-]+' | head -1 | cut -d: -f2)"
topic_arg="$(printf '%s\n' "$raw_args" | sed -E 's/[[:space:]]*space:[A-Za-z0-9_-]+[[:space:]]*/ /g' | sed -E 's/^[[:space:]]+|[[:space:]]+$//g')"
# The resolver ships inside the installed plugin; the relative path only
# exists in a wenlan checkout.
resolver="$(find "$HOME/.codex/plugins/cache" -path '*/wenlan/*/bin/resolve-space.sh' 2>/dev/null | head -1)"
resolved="$("${resolver:-plugin-codex/bin/resolve-space.sh}" --cwd "$PWD" ${space_arg:+--arg "$space_arg"} 2>/dev/null)"
space="$(printf '%s\n' "$resolved" | cut -f1)"
source_layer="$(printf '%s\n' "$resolved" | cut -f2)"

Print `Resolved space: <space> (from <source-layer>)`. If no Space resolves, print `Resolved space: none (unscoped)` and omit `space`.

2. Read the Brief

Call:

mcp__wenlan__brief(
  topic="<topic_arg only when the user supplied one>",
  space="<resolved only when non-empty>"
)

Do not invent or infer a topic when the argument is absent. No topic means the complete Brief alone. A topic means the same complete Brief plus a separate `Related Context` section scoped to that Space.

Brief reads never create state. If the state is `brief_not_created`, explain that the first `/handoff` update will create it. If the state is `space_not_resolved`, ask for a Space only when the working directory and configuration cannot resolve one safely.

Render the last-session summary, Active, Backlog, then Related Context only when returned. Keep stable item IDs and versions available for later `/handoff` reconciliation, but omit them from the normal user-facing list.

3. Pending revisions

Call:

mcp__wenlan__list_pending_revisions(limit=10)

If empty, say nothing. If it fails, emit one warning and keep the Brief. If non-empty, show at most three. Never auto-action them.

  • accept: `mcp__wenlan__accept_revision(target_source_id="<id>")`
  • dismiss: `mcp__wenlan__dismiss_revision(target_source_id="<id>")`
  • skip: no call

If more than three exist, point to `/curate revisions`.

Boundary

Use `/brief` to resume a Space or answer "catch me up." It is not a mandatory every-session boot step. Use `/recall` for a specific fact, `/capture` for a durable memory, and `/handoff` to close a work session.

Read more
Ships withwenlan

Wenlan is a knowledge base for the AI-native age. Your AI agents capture what they learn, Wenlan keeps it current and distills it into source-cited wiki pages you can trust

Get the whole plugin

Other skills on wenlan.

prove
Skill

prove

Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly sweep. Routes to scripts; every check…

@7xuanlu@7xuanluView Skill
verify
Skill

verify

Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects;…

@7xuanlu@7xuanluView Skill
capture
Skill

capture

Save a durable memory to Wenlan from Codex. Use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact.…

@7xuanlu@7xuanluView Skill
curate
Skill

curate

Review pending Wenlan captures, revisions, or daemon refinements from Codex. Use for explicit audit walks after /brief or /handoff surfaces pending work.…

@7xuanlu@7xuanluView Skill