Project Folder Structure
Every project gets a consistent folder structure in Google Drive. The project folder contains a subfolder for each skill, and each skill folder contains a subdirectory per deliverable:
Each skill’s work lives in its own folder, named with the full skill slug. Inside, each deliverable has its own subdirectory containing the deliverable’s files. You always know where to find a deliverable — it’s in the folder that matches the skill, then the subfolder that matches the deliverable.
What’s Inside a Deliverable Folder
Every deliverable subdirectory contains at least two files:
Markdown (.md) — The working source file. This is what downstream skills read from. The markdown is the source of truth.
Google Doc (.gdoc) — The collaboration version in Google Docs. Leave comments, suggest edits, track changes. Usually where review happens.
Deliverables with visual output — like the sitemap or wireframes — additionally carry .svg asset files and exports (e.g. a Slickplan .xml) inside the same subdirectory.
Naming Conventions and Versions
Every file follows the same naming pattern:
For example: acme-website-project-brief.md, acme-website-voice-guide.pdf.
When a deliverable is revised, the current version stays in place with the same filename. Previous versions are moved to a previous-versions/ subfolder within the skill's folder, so you always have the revision history available without cluttering the main folder.