storage-function-structure
File Structure for Project Planning Artifacts
- [Planning Artifact] are stored in dedicated directories based on their type, with each file named using a short hash and a descriptive title.
- These directories are typically stored in a parent folder. defer to the storage backend conventions for exact paths.
Directory and File Naming Conventions
-
Each planning artifact type has its own directory:
Prd/for Product Requirements DocumentsEpic/for EpicsSpec/for SpecificationsStory/for User StoriesTask/for TasksDecision/for DecisionsResearch/for Research DocumentsRetro/for Retrospectives
-
Files within these directories are named using the format:
<short-hash>-<descriptive-title>.md
More from zenobi-us/dotfiles
leaflet-mapping
Use when creating interactive maps in Obsidian using LeafletJS plugin - covers real-world maps, image maps, markers from notes, overlays, GeoJSON, GPX tracks, and common issues with bounds/zoom levels
73skill-hunter
Find and download skills. Use when you need to discover existing skills from GitHub repositories and store them in the correct local skills category. Results in discovered skills being downloaded into the users dotfile repo.
68using-superpowers
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
67deep-researcher
Use when delegating research tasks requiring verified information from multiple authoritative sources - crawls and fact-checks beyond surface-level findings, providing evidence of verification process with confidence levels for each claim
66chrome-debug
Use when debugging web applications in chrome via the remote debugging protocol. Provides capabilities for inspecting DOM, executing JS, taking screenshots, and automating browser interactions.
64projectmanagement
Skills for managing projects, tracking progress, and suggesting next actions.
64