Skip to content
Skills Library
Management & product · Automation

refresh

/refresh

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".

Licence
MIT
Last repository change
14.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/detect_context_drift.py, scripts/shared.py

What it does and when to use it

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".

Triggers from the description

refresh contextupdate contextinit roadmapstale contextscaffold roadmap

Arguments

/refresh [init | check | all | project | architecture | documents]
Original author description

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".

How it works

  1. Arguments
  2. Step 1: Run Drift Detection
  3. Step 2: Context Discovery
  4. Step 3: Generate Files
  5. Step 4: Confirm and Write
  6. References
Original SKILL.md headings · 102 lines, 455 words
SKILL.md preview
---
name: refresh
description: >
  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".
disable-model-invocation: true
argument-hint: "[init | check | all | project | architecture | documents]"
allowed-tools: Read, Glob, Grep, Write, Bash
---

# Context Directory Refresh

Detect drift in `.arkhe/roadmap/` context files and regenerate them using a hybrid format (condensed summary + references to authoritative docs).

## Arguments

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 |

## Step 1: Run Drift Detection

Run the detection script:

```bash
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.

## Step 2: Context Discovery

For `init`, `all`, or single-file modes, run the shared context discovery protocol from [CONTEXT_DISCOVERY.md](../../references/CONTEXT_DISCOVERY.md). Gather:

- From `README.md`: project purpose, target users
- From `CLAUDE.md`: constraints, conventions, tech stack
- From build files: tech stack detection via [TECH_STACK_DETECTION.md](../../references/TECH_STACK_DETECTION.md)
- From `docs/**/*.md`: documentation inventory
- From module globs: module inventory with file counts
- From `docs/adr/**/*.md`: ADR titles and status
- From `arkhe/specs/*/spec.md`: spec pipeline

## Step 3: Generate Files

Generate each requested file using the hybrid format below. See [WORKFLOW.md](WORKFLOW.md) for detailed generation protocol per file.

### Hybrid Format Template

```markdown
# {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}
```

### Generation Sources

| 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 |

## Step 4: Confirm and Write

Before writing each file:

1. Show current content (if exists) or "Does not exist"
2. Show proposed new content
3. Ask: **"Write this to `{context_dir}/{filename}`?"**

Create the `.arkhe/roadmap/` directory if it doesn't exist.

Never overwrite without confirmation.

## References

- [WORKFLOW.md](WORKFLOW.md) — Detailed generation protocol per file
- [EXAMPLES.md](EXAMPLES.md) — Usage examples
- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) — Common issues
Files in this package (6)
  • EXAMPLES.md 3 KB
  • SKILL.md 4 KB
  • TROUBLESHOOTING.md 2 KB
  • WORKFLOW.md 6 KB
  • scripts/detect_context_drift.py 5 KB
  • scripts/shared.py 8 KB

Versions

RepositoryScoreLicence
This page · joaquimscosta/arkhe-claude-plugins100MIT
tony/skills100MIT
HarishTeens/fingod100Apache-2.0
fullymiddleaged/clawness100MIT
prathikcannotcode/Vigil100Apache-2.0
naveedharri/benai-skills100MIT
adelrodriguez/skills96MIT

Database snapshot: 13.11.2026 · package version 22acc56d5b8d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100refresh-claude-md
    Use when the project's CLAUDE.md is stale or missing and must be regenerated from the current codebase — re-detect tech stack, commands, conventions, and structure, then update CLAUDE.md while preserving every human-authored customization. Adapted from the ECC codebase-onboarding skill.
  • 100drift-detect
    Use when roadmap, plans, or docs may have drifted from code, or when restarting a stalled project. Not for PR doc sync: use docs-update.
  • 96sync-roadmap
    Reconcile ROADMAP.md checkbox state against on-disk SUMMARY.md presence. Default: silently corrects drift; --dry-run previews; --interactive prompts per change. Triggers on: "sync roadmap", "reconcile roadmap", "fix roadmap drift", "is the roadmap accurate".
  • 90refresh-context
    Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is…
  • 92review-roadmap
    Review a roadmap in a fresh agent before lock. Use for /review-roadmap.
  • 90roadmap-management
    Use when the user says \"create roadmap\", \"show roadmap\", or \"execute roadmap\". Creates, reads, and manages roadmap files with phase tracking.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.