Directory Management

by awslabs097fe8ad56d8No license915 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

Instructions onlyProductivity & Workflow
AI-generated overview

Sets up and organizes a project directory structure and resolves project naming before work begins.

What it does
This skill guides the agent through resolving a project name, either from conversation context, by scanning for existing PLAN.md files, or by recommending a lowercase slug for user confirmation. It then creates and uses a project directory containing specs/, scripts/, notebooks/, manifests/, and agent_memory/ subfolders for storing generated artifacts. It also describes how a PLAN.md is associated with a project directory and how session notes persist progress.
When to use it
Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. It is meant to establish naming and folder structure before any other work begins.
Requirements
No scripts or special tools are required; it is instructions only and relies on the agent's file access to scan for PLAN.md files and create directories.

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

Source and attribution

Source:awslabs/agent-pluginsinplugins/sagemaker-ai/skills/directory-managementat commit097fe8a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal