awslabs/directory-management
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agent_memory/) and resolves project naming.
npx skills add https://github.com/awslabs/agent-plugins --skill directory-management
Before any work begins, resolve the project name:
*/PLAN.md files in the current directory. If found, ask the user if they are resuming an existing project and load that PLAN.md into context.[a-z0-9-]), or ask directly if there isn't enough context. Present the recommended name and wait for user confirmation.Once project name is resolved:
<experiment-name>/ directory using the confirmed name for storing all the artifactsWhen working with the agent, all generated files are organized under an project directory.
<project-name>/
├── specs/
│ ├── PLAN.md # Your customization plan
├── scripts/ # Generated Python scripts
│ ├── <project-name>_transform_fn.py
├── notebooks/ # Generated Jupyter notebooks
│ ├── <project-name>.ipynb
├── manifests/ # Machine-readable outputs (JSON)
└── agent_memory/ # Session persistence (git-ignored)
└── session-notes.md # Progress, artifacts, next steps
Take awslabs/directory-management from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.