# directory-management

Sets up a project folder with specs, scripts, notebooks, manifests and agent memory folders, and picks a name for the project.

Skill by Amazon Web Services. Category: Agent craft.

## Install

Project (for this project only):

```sh
npx skills add awslabs/agent-plugins --skill directory-management
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add awslabs/agent-plugins --skill directory-management -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass
- ZeroLeaks: Pass

Installs: 174. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/awslabs/agent-plugins/directory-management)

## Source

[Open the source](https://github.com/awslabs/agent-plugins/tree/HEAD/plugins/sagemaker-ai/skills/directory-management). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: directory-management
description: 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.
metadata:
  version: "1.0.0"
---

# Directory Management

## Project Setup

Before any work begins, resolve the project name:

1. If the project name is already known from conversation context, use it.
2. Otherwise, scan for existing `*/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.
3. If no existing projects are found, recommend a ≤64-char lowercase slug based on what you know from the conversation (only `[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:

1. Create and/or use the `<experiment-name>/` directory using the confirmed name for storing all the artifacts

## Directory Structure

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

- Previous: [deploy](https://syn4pse.dev/terminal/agent-plugins-deploy.md)
- Next: [use-case-specification](https://syn4pse.dev/terminal/use-case-specification.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
