Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Detect drift in .arkhe/roadmap/ context files and regenerate them using a hybrid format (condensed summary + references to authoritative docs).
Parse from $ARGUMENTS:
| Mode | Description |
|---|---|
init | Scaffold .arkhe/roadmap/ with all 3 files from scratch |
check | Detect drift only — report staleness, don't write |
all | Regenerate all 3 context files |
project | Regenerate only project.md |
architecture | Regenerate only architecture.md |
documents | Regenerate only documents.md |
| (none) | Run check, then ask which files to refresh |
Run the detection script:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/refresh/scripts/detect_context_drift.py .
Parse the JSON output. Present a drift report table:
## Context Directory Status
| File | Exists | Staleness | Days | Commits Since | feat/fix |
|------|--------|-----------|------|---------------|----------|
| project.md | Yes/No | fresh/aging/stale/very_stale | N | N | N |
| architecture.md | Yes/No | ... | ... | ... | ... |
| documents.md | Yes/No | ... | ... | ... | ... |
New modules not in architecture.md: {list or "none"}
For check mode: Stop here. Present the report and suggest which files need attention.
For init, all, or single-file modes, run the shared context discovery protocol from CONTEXT_DISCOVERY.md. Gather:
README.md: project purpose, target usersCLAUDE.md: constraints, conventions, tech stackdocs/**/*.md: documentation inventorydocs/adr/**/*.md: ADR titles and statusarkhe/specs/*/spec.md: spec pipelineGenerate each requested file using the hybrid format below. See WORKFLOW.md for detailed generation protocol per file.
# {Title}
_Auto-generated by /roadmap:refresh on {date}. Edit freely — regenerate with `/roadmap:refresh {file}`._
## Summary
{3-5 bullet points, <300 tokens — the essential facts}
## Details
{Structured data: tables, lists}
## References
{Pointers to authoritative docs}
- `{doc_path}` — {one-line description}
| File | Primary Sources |
|---|---|
project.md | README.md, CLAUDE.md, gap analyses, existing project.md |
architecture.md | Build files, module globs, ADRs, CLAUDE.md architecture section |
documents.md | Phase 5 doc scan results, spec files, gap analyses, ADRs |
Before writing each file:
{context_dir}/{filename}?"Create the .arkhe/roadmap/ directory if it doesn't exist.
Never overwrite without confirmation.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
The English summary is being prepared. Showing the original description.
Analyze system architecture, module structure, API contracts, data models, and code patterns. Use when designing systems, reviewing module boundaries, evaluating API designs, analyzing data models, checking pattern conformance, tracing decisions, or reviewing frontend architecture. Triggers: "architecture", "module design", "API design", "data model", "boundaries", "patterns", "decisions", "frontend architecture".
The English summary is being prepared. Showing the original description.
Converts natural-language descriptions or UI spec files into optimized Google Stitch prompts. Use when creating, refining, or validating design directives for Google Stitch. Use when user says "create a Stitch prompt", "optimize this for Stitch", "convert this spec to a Stitch prompt", "write a UI prompt", or mentions Google Stitch prompt authoring. Follows Stitch best practices with short, directive prompts focused on screens, structure, and visual hierarchy.
The English summary is being prepared. Showing the original description.
Zero-dependency live-preview server providing an agent↔browser bidirectional companion. Watches a content directory, wraps HTML fragments in a frame template, broadcasts live-reload over WebSocket, and captures browser-side click events to a JSONL file. Use when an agent needs to show HTML to the user in a browser and react to clicks — mockups, design exploration, gallery browsing, multi-select choices, prototype iteration. Triggered by "live preview", "browser companion", "preview server", "browser mockup", "show in browser", "arkhe-preview", or any skill that wants to write HTML fragments and have the user see them reload in real time.
The English summary is being prepared. Showing the original description.
Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.
The English summary is being prepared. Showing the original description.
Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".
The English summary is being prepared. Showing the original description.