← CmdBriefCONTENT HISTORY
WHAT CHANGED
Update to CmdBrief
Snapshot Oct 28, 2026 · 13:11 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save CmdBrief and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "First-run setup for the CmdBrief plugin. Checks that CmdBrief on the user's Mac is reachable, lists its workspaces and shows the user how to plan and send a project.",
"included_files": [],
"name": "setup",
"skill_md_contents": "---\nname: setup\ndescription: First-run setup for the CmdBrief plugin. Checks that CmdBrief on the user's Mac is reachable, lists its workspaces and shows the user how to plan and send a project.\n---\n\n# Set up CmdBrief\n\n1. Call `cmdbrief_home`. If it reports CmdBrief is not running, tell the user\n what CmdBrief needs, in three short lines:\n - CmdBrief for Mac, open and signed in to the same CmdBrief account they\n connected here.\n - **ChatGPT in the cloud** turned on in CmdBrief's Settings > Account.\n - Then ask again. Plans sent before that wait for CmdBrief for up to 7\n days.\n2. Otherwise tell the user which workspaces CmdBrief has, in one line.\n3. Explain the flow in three short lines:\n - Ask me to plan a project; I open the Project plan beside the chat.\n - Edit it there, then press **Send to CmdBrief** or ask me to send it.\n - Confirm it in CmdBrief and press Start. Nothing starts before that.\n4. Offer a first prompt, for example \"Plan a small landing page for my side\n project\", and mention the CmdBrief entry in the sidebar for crew status.\n"
}SHA-256 of public snapshot: 423ca9832feb2ecc19b8028a116c83688a1278895e01c79ae1129122f60c406f