Philosophy: All code is a Project. Knowledge lives in Areas. Tools live in Resources.
📂 Workspace Structure
workspace/
├── _inbox/ # 📥 Unprocessed items, quick capture
├── Projects/ # ⚡ Active development projects (with deadlines)
│ └── my-app/ # Each project: kebab-case, has project.md
│ ├── project.md # Project contract (goal, deadline, DoD)
│ ├── repo/ # Source code (git root)
│ ├── sessions/ # Session logs & BACKLOG.md
│ ├── docs/ # Project documentation
│ └── artifacts/ # AI-generated artifacts
│ ├── plans/ # 📝 Implementation plans
│ └── tasks/
│ ├── backlog.md # 📌 CANONICAL task list
│ ├── sprint-current.md
│ └── done.md
├── Areas/
│ ├── infra/ # 🔧 Infrastructure SOPs, runbooks, configs
│ ├── product/ # 📦 Product specs, design decisions
│ └── ops/ # ⚙️ Operations, CI/CD, deployment
├── Resources/
│ ├── ai-agents/ # 🤖 Kernel snapshot, agent workflows
│ │ ├── kernel/
│ │ └── workflows/
│ ├── references/ # 📚 Reference repos, docs, cheat-sheets
│ └── tools/ # 🛠️ Scripts, utilities, CLI tools
├── Archive/ # ❄️ Completed/retired projects & areas
├── .agent/ # Agent runtime (auto-installed)
│ ├── rules/
│ └── workflows/
├── .para-workspace.yml # Workspace config
├── para # CLI wrapper (auto-generated)
└── README.md📑 Recommended Workflows
| Workflow | When to Use |
|---|---|
/plan | Create or review an implementation plan |
/open | Start a working session, load context |
/backlog | Add/prioritize tasks for a project |
/docs | Generate, review, and publish technical documentation |
/new-project | Scaffold a new development project |
/learn | Document lessons and knowledge in Areas |
/push | Quick commit and push to GitHub |
/verify | Verify a feature is complete via walkthrough |
/release | Pre-release quality gate before publishing |
/retro | Retrospective before archiving a project |
/end | Close session and log progress |
/para | Workspace health check and maintenance |
📜 Active Rules
After para init, the following rules are installed in .agent/rules/:
governance.md— Core PARA discipline rules (invariants + heuristics)
💡 Tips for dev Profile
- kebab-case everything:
my-app,auth-service,api-gateway - One git repo per Project folder: the
repo/sub-folder is the git root _inbox/is your capture zone: drop notes, code snippets, links here — process later during/end- Areas are evergreen SOPs: runbooks in
Areas/infra/should always be accurate - Resources are read-only references: don’t do active work inside
Resources/