archive
Bundle the finished John workspace (PLAN.md, CLAUDE.md, AGENTS.md, .john/, .claude/skills/, .agents/skills/) into a release zip. Use when the user says…
Print John workspace status — active template, current phase, inventory of inputs/parsed/chunks/knowledge/events/checkpoints/produced-skills. Use whenever the user asks "where are we?", "what's done?", "what's next?", or you need to verify state before advancing a phase. Cheap;
> /plugin marketplace add kitchen-engineer42/joharnessburg > /plugin install john@joharnessburg
How it fires
How this command gets triggered: by you, by Claude, or both.
/statusContext preview
What this command does when you run it.
Print John workspace status — active template, current phase, inventory of inputs/parsed/chunks/knowledge/events/checkpoints/produced-skills. Use whenever the user asks "where are we?", "what's done?", "what's next?", or you need to verify state before advancing a phase. Cheap;
description: Print John workspace status — active template, current phase, inventory of inputs/parsed/chunks/knowledge/events/checkpoints/produced-skills. Use whenever the user asks "where are we?", "what's done?", "what's next?", or you need to verify state before advancing a phase. Cheap; run it generously.
When this command fires:
1. Invoke the status script via Bash:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/workspace_status.py"2. The script emits JSON to stdout and a human-readable summary to stderr. Show the user the human-readable summary directly. Use the JSON to decide your own next action (e.g., advance phase, dispatch subagents).
3. On `success: false` with "No .john/ directory found", tell the user to run `/john:init` first to scaffold the workspace.
After showing the status, if the user is asking "what's next?", consult `PLAN.md` (read the file) to identify the next incomplete phase and propose advancing it per the `ralph-loop` skill.
中文版: README_ZH.md John turns unstructured source material into a working knowledge-dense app. It keeps knowledge engineering and app building in one durable run, coordinates large per-entry fan-outs, and leaves auditable events and checkpoints on disk.
Bundle the finished John workspace (PLAN.md, CLAUDE.md, AGENTS.md, .john/, .claude/skills/, .agents/skills/) into a release zip. Use when the user says…
Set or clear the long-running goal for this John session. Pinned into the system prompt by the SessionStart hook so it survives context compaction and stays…
Scaffold the John workspace in the current project. Creates .john/ working state, a starter PLAN.md, and (if missing) a starter CLAUDE.md. Optionally copies an…
Assemble a run report — the shareable postmortem of this John run (process scorecard + manifest + outcome summary + candidate lessons), privacy-scrubbed. Use…