
Directory Management
This handles the tedious part of starting or resuming a Claude project by creating a consistent folder structure (specs, scripts, notebooks, manifests, agent_memory) and resolving what to call everything. It checks for existing PLAN.md files first so you don't accidentally create duplicates, then either uses context from your conversation or asks you to confirm a slugified project name. The structure is opinionated but sensible, keeping generated code separate from plans and using agent_memory for session notes that stay out of git. It's the kind of thing you'd otherwise copy-paste from project to project or forget to do until you have files scattered everywhere.
- skills.sh installs
- 183
- GitHub stars
- 938
- last updated
- Jun 11, 2026
Install
$ npx -y skills add awslabs/agent-plugins --skill directory-management --agent claude-codeInstalls into .claude/skills of the current project.
Files
Directory Management
Project Setup
Before any work begins, resolve the project name:
- If the project name is already known from conversation context, use it.
- Otherwise, scan for existing
*/PLAN.mdfiles in the current directory. If found, ask the user if they are resuming an existing project and load thatPLAN.mdinto context. - 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:
- 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.
Sponsors
Details
- Repository
- github.com/awslabs/agent-plugins
- Categories
- Code Review & Quality, AI & Agent Building, Productivity & Planning
- License
- Apache-2.0
- First seen
- Jun 11, 2026
More from awslabs/agent-plugins
All 32- Use Case Specification183
- Planning168
- Dataset Evaluation156
- Aws Serverless Deployment154
- Finetuning154
- Model Deployment154
- Dataset Transformation153
- Hyperpod Ssm150
- Hyperpod Version Checker149
- Hyperpod Issue Report147
- Model Evaluation140
- Amplify Workflow101
- Amazon Location Service
- Api Gateway
- Aws Lambda Durable Functions
- Aws Lambda Managed Instances
- Aws Transform
- Document Service
- Dsql
- Elastic Beanstalk
- Finetuning Technique
- Hyperpod Cluster Debugger
- Hyperpod Nccl
- Hyperpod Node Debugger