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".
What this skill does
# 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.