update-workspace-map_skill

This skill validates 04-workspace structure against workspace-map.md up to 3 levels, ensuring accurate documentation and guiding comprehensive updates.

Python

2

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill abdullahbeam/nexus-design-abdullah --skill update-workspace-map

README.md7.2 KB
SKILL.md4.7 KB

Overview

This skill validates that workspace-map.md accurately documents the actual 04-workspace/ folder structure up to three levels deep. It detects mismatches, undocumented files, and hierarchy errors, then produces a clear, depth-indicated report and actionable update guidance. Use it to keep AI navigation reliable after reorganizations.

How this skill works

The skill scans 04-workspace/ to collect the actual directory tree and important markdown/README files (max depth = 3). It parses workspace-map.md for the documented tree and folder descriptions, then performs a hierarchical comparison across level 1–3 paths. Results include missing or extra folders, parent/child mismatches, and warnings for important files that lack documentation.

When to use it

After reorganizing folders inside 04-workspace/
When AI agents fail to locate expected folders or contents
During onboarding or handoffs to verify documentation (e.g., Project 03, Task 5.6)
As part of regular maintenance or on close-session triggers
Before running automation that relies on documented workspace paths

Best practices

Run the validation immediately after folder moves, renames, or bulk imports
Keep workspace-map.md updated with both the tree view and folder descriptions to enable cross-reference
Exclude hidden/system folders from documentation and the scan to reduce noise
Document notable markdown/README files so the skill can warn if important files are undocumented
Use the report’s depth indicators to apply targeted changes rather than sweeping edits

Example use cases

You moved client folders into a new parent and need to update workspace-map.md to reflect new nesting
You added templates and example directories; validate they appear and have descriptions
Routine close-session check flags a missing level-2 folder introduced during a sprint
Onboarding a new teammate: confirm the documented map matches actual workspace layout
Prepare for an automation run that relies on precise 3-level paths

FAQ

It scans and validates up to three directory levels beneath 04-workspace/ (root → level 1 → level 2 → level 3).

Will it modify workspace-map.md automatically?

No. It produces a detailed, actionable report and prompts to guide manual updates and final validation.

Which files trigger undocumented-file warnings?

Markdown files and README* files found within the three-level scan are flagged if they lack corresponding documentation in workspace-map.md.