Subchapter 24.11
references/directory-management/overview.mdMarkdown2 KBView on GitHub
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.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.
Ask for confirmation. Derive a ≤64-char lowercase slug ([a-z0-9-] only) from the conversation context and present it to the user as a question — for example: “I’ll use my-project-name as the project folder — does that work, or would you prefer something different?” End your response there. Do not create the directory in this step.
⏸ Wait for the user’s reply before proceeding.
Create the directory. Once the user confirms the name (or provides an alternative), create the <project-name>/ directory and its subdirectories.
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)