65 lines
1.6 KiB
Markdown
65 lines
1.6 KiB
Markdown
# Example Project Profile
|
|
|
|
## Purpose
|
|
|
|
Non-sensitive example profile showing how a new project can reuse the workspace core without inheriting another project's context.
|
|
|
|
---
|
|
|
|
## Project
|
|
|
|
- Name: Example Project
|
|
- Workspace role: companion AI workspace
|
|
- Primary use: memory, status drafting, work-item tracking, and communication polishing
|
|
|
|
---
|
|
|
|
## Communication Sources
|
|
|
|
- Live communication: configure a connector if needed
|
|
- Historical archive: optional
|
|
- Recommended generic variables:
|
|
- `AIW_PROJECT_PROFILE=example`
|
|
- `AIW_PROJECT_KNOWLEDGE_DIR=<optional custom project knowledge path>`
|
|
- `AIW_CHANNEL_PREFIX=example`
|
|
- `AIW_MATTERMOST_SYNC_CMD=<optional>`
|
|
- `AIW_SLACK_EXPORT_PATH=<optional>`
|
|
|
|
---
|
|
|
|
## Work System
|
|
|
|
- Use `project-knowledge/02-work-items/` for active units of work
|
|
- Use `project-knowledge/01-current/work-items.md` for the active summary
|
|
- Use any ticket ID format relevant to the project
|
|
- Keep approved titles or explicit task names visible for recurring updates
|
|
|
|
---
|
|
|
|
## Context
|
|
|
|
Project-specific durable context should live under `workspaces/example/project-knowledge/03-context/`.
|
|
|
|
People, decisions, daily notes, maps, and templates should live under the corresponding `workspaces/example/project-knowledge/` folders.
|
|
|
|
Do not place company secrets, raw exports, credentials, or private communication transcripts in the profile.
|
|
|
|
---
|
|
|
|
## Suggested Commands
|
|
|
|
- `/workspace-context`
|
|
- `/communication-sync`
|
|
- `/archive-import`
|
|
- `/standup`
|
|
- `/manager-update`
|
|
- `/translate`
|
|
- `/ai-prompt`
|
|
|
|
## Suggested Generic Skills
|
|
|
|
- `workspace-memory-curation`
|
|
- `professional-communication`
|
|
- `status-reporting`
|
|
- `ai-prompt-engineering`
|