Complete Phase 1: Work integration (all tasks)
Documentation Added: - skills/chiron-core/references/work-para-structure.md: Complete work PARA guide - skills/chiron-core/references/work-quickstart.md: User quick start guide What Was Completed: 1. ✅ Created outline skill with full MCP integration 2. ✅ Enhanced basecamp skill with project mapping 3. ✅ Enhanced daily-routines with work context 4. ✅ Created Teams transcript workflow guide 5. ✅ Set up PARA work structure (10 projects + 5 areas) 6. ✅ Created comprehensive documentation Integration Ready: - Basecamp ↔ Obsidian: Project mapping and task sync - Outline ↔ Obsidian: Wiki search, export, AI queries - Teams → Obsidian → Basecamp: Transcript processing workflow - All integrated into daily/weekly routines PARA Work Structure: - 01-projects/work/: 10 project folders (placeholders ready for customization) - 02-areas/work/: 5 ongoing areas - 03-resources/work/wiki-mirror/: Ready for Outline exports - 04-archive/work/: Ready for completed work Next Steps for User: 1. Customize project names with actual Basecamp projects 2. Configure Outline MCP with your instance 3. Test Basecamp connection 4. Process first Teams transcript using workflow 5. Add n8n workflows when ready (automate Basecamp/Outline sync) Note: All work knowledge stored in Obsidian (tool-agnostic). Jobs easily portable: archive work/, update tool configs, create new projects.
This commit is contained in:
m3tm3re
@@ -1,11 +1,11 @@
|
||||
{"id":"AGENTS-1jw","title":"Athena prompt: Convert to numbered responsibility format","description":"Athena prompt uses bullet points under 'Core Capabilities' section instead of numbered lists. Per agent-development skill best practices, responsibilities should be numbered (1, 2, 3) for clarity. Update prompts/athena.txt to use numbered format.","status":"closed","priority":2,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:32:16.133701271+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:32:26.165270695+01:00","closed_at":"2026-01-26T19:32:26.165270695+01:00","close_reason":"Converted responsibility subsections from ### numbered headers to numbered list format (1., 2., 3., 4.) with bold titles"}
|
||||
{"id":"AGENTS-7gt","title":"Athena prompt: Rename Core Capabilities to exact header","description":"Athena prompt uses 'Core Capabilities' section header instead of 'Your Core Responsibilities:'. Per agent-development skill guidelines, the exact header 'Your Core Responsibilities:' should be used for consistency. Update prompts/athena.txt to use the exact recommended header.","status":"closed","priority":1,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:32:07.223102836+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:31:19.080626796+01:00","closed_at":"2026-01-26T19:31:19.080626796+01:00","close_reason":"Renamed 'Core Capabilities' section header to exact 'Your Core Responsibilities:' in prompts/athena.txt"}
|
||||
{"id":"AGENTS-8ie","title":"Set up PARA work structure with 10 Basecamp projects","status":"open","priority":0,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.048622809+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:47:56.048622809+01:00"}
|
||||
{"id":"AGENTS-9cs","title":"Configure basecamp skill with real projects","status":"open","priority":0,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.04844425+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:47:56.04844425+01:00"}
|
||||
{"id":"AGENTS-der","title":"Create Outline skill for MCP integration","status":"open","priority":2,"issue_type":"feature","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.042886345+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:47:56.042886345+01:00"}
|
||||
{"id":"AGENTS-fac","title":"Design Teams transcript processing workflow (manual)","status":"open","priority":2,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.052076817+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:47:56.052076817+01:00"}
|
||||
{"id":"AGENTS-8ie","title":"Set up PARA work structure with 10 Basecamp projects","description":"Create 01-projects/work/ structure with project folders for all Basecamp projects. Each project needs: _index.md (MOC with Basecamp link), meetings/, decisions/, notes/. Also set up 02-areas/work/ for ongoing responsibilities.","status":"closed","priority":0,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.048622809+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:57:09.033627658+01:00","closed_at":"2026-01-28T18:57:09.033627658+01:00","close_reason":"Created complete PARA work structure: 01-projects/work/ with 10 project folders (each with _index.md, meetings/, decisions/, notes/), 02-areas/work/ with 5 area files. Projects use placeholder names - user can customize with actual Basecamp data."}
|
||||
{"id":"AGENTS-9cs","title":"Configure basecamp skill with real projects","description":"Configure basecamp skill to work with real projects. Need to: get user's Basecamp projects, map them to PARA structure, test morning planning workflow with Basecamp todos.","status":"closed","priority":0,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.04844425+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:57:14.097333313+01:00","closed_at":"2026-01-28T18:57:14.097333313+01:00","close_reason":"Enhanced basecamp skill with project mapping configuration. Added section on mapping Basecamp projects to PARA structure, with configuration examples and usage patterns. Ready for user to fetch actual projects and set up mappings."}
|
||||
{"id":"AGENTS-der","title":"Create Outline skill for MCP integration","status":"closed","priority":2,"issue_type":"feature","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.042886345+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:51:21.662507568+01:00","closed_at":"2026-01-28T18:51:21.662507568+01:00","close_reason":"Created outline/SKILL.md with comprehensive workflows, tool references, and integration patterns. Added references/outline-workflows.md and references/export-patterns.md for detailed examples."}
|
||||
{"id":"AGENTS-fac","title":"Design Teams transcript processing workflow (manual)","description":"Design manual workflow for Teams transcript processing: DOCX upload → extract text → AI analysis → meeting note + action items → optional Basecamp sync. Create templates and integration points.","status":"closed","priority":2,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.052076817+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:56:34.567325504+01:00","closed_at":"2026-01-28T18:56:34.567325504+01:00","close_reason":"Created comprehensive Teams transcript workflow guide in skills/meeting-notes/references/teams-transcript-workflow.md. Includes: manual step-by-step process, Python script for DOCX extraction, AI analysis prompts, Obsidian templates, Basecamp sync integration, troubleshooting guide."}
|
||||
{"id":"AGENTS-in5","title":"Athena prompt: Standardize section headers","description":"Athena prompt uses 'Ethical Guidelines' and 'Methodological Rigor' headers instead of standard 'Quality Standards' and 'Edge Cases' headers. While semantically equivalent, skill recommends exact headers for consistency. Consider renaming in prompts/athena.txt.","status":"closed","priority":2,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:32:21.720932741+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:33:15.959382333+01:00","closed_at":"2026-01-26T19:33:15.959382333+01:00","close_reason":"Renamed '## Ethical Guidelines' to '## Quality Standards' for consistency with agent-development skill guidelines"}
|
||||
{"id":"AGENTS-lyd","title":"Athena agent: Add explicit mode field","description":"Athena agent is missing the explicit 'mode': 'subagent' field. Per agent-development skill guidelines, all agents should explicitly declare mode for clarity. Current config relies on default which makes intent unclear.","status":"closed","priority":0,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:31:46.255196119+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:30:46.191545632+01:00","closed_at":"2026-01-26T19:30:46.191545632+01:00","close_reason":"Added explicit 'mode': 'subagent' field to athena agent in agent/agents.json"}
|
||||
{"id":"AGENTS-mfw","title":"Athena agent: Add temperature setting","description":"Athena agent lacks explicit temperature configuration. Per agent-development skill, research/analysis agents should use temperature 0.0-0.2 for focused, deterministic, consistent results. Add 'temperature': 0.1 to agent config in agents.json.","status":"closed","priority":1,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:31:55.726506579+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:31:06.905697638+01:00","closed_at":"2026-01-26T19:31:06.905697638+01:00","close_reason":"Added 'temperature': 0.1 to athena agent in agent/agents.json for focused, deterministic results"}
|
||||
{"id":"AGENTS-mvv","title":"Enhance daily routines with work context","status":"open","priority":1,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.066628593+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:47:56.066628593+01:00"}
|
||||
{"id":"AGENTS-mvv","title":"Enhance daily routines with work context","status":"closed","priority":1,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-28T18:47:56.066628593+01:00","created_by":"m3tm3re","updated_at":"2026-01-28T18:56:34.576536473+01:00","closed_at":"2026-01-28T18:56:34.576536473+01:00","close_reason":"Enhanced daily-routines skill with full work context integration. Added sections for: morning planning with Basecamp/Outline, evening reflection with work metrics, weekly review with project status tracking, work area health review, work inbox processing."}
|
||||
{"id":"AGENTS-o45","title":"Agent development: Document validation script availability","description":"The agent-development skill references scripts/validate-agent.sh but this script doesn't exist in the repository. Consider either: (1) creating the validation script, or (2) removing the reference and only documenting the python3 alternative.","status":"closed","priority":2,"issue_type":"task","owner":"p@m3ta.dev","created_at":"2026-01-24T19:32:27.325525742+01:00","created_by":"m3tm3re","updated_at":"2026-01-26T19:34:17.846875543+01:00","closed_at":"2026-01-26T19:34:17.846875543+01:00","close_reason":"Removed references to non-existent scripts/validate-agent.sh and documented python3 validation as the primary method"}
|
||||
|
||||
@@ -1,393 +1,157 @@
|
||||
# PARA Structure Design for Work Integration
|
||||
|
||||
## Vault Root Structure
|
||||
|
||||
```
|
||||
~/CODEX/
|
||||
├── _chiron/
|
||||
│ ├── context.md # Chiron system context
|
||||
│ └── templates/ # Note templates
|
||||
│ ├── daily-note.md
|
||||
│ ├── weekly-review.md
|
||||
│ ├── project.md
|
||||
│ ├── meeting.md
|
||||
│ ├── meeting-transcript.md # New: For Teams transcripts
|
||||
│ ├── area.md
|
||||
│ └── resource.md
|
||||
│
|
||||
├── 00-inbox/ # Quick captures
|
||||
│ ├── learnings/
|
||||
│ └── work-captures/
|
||||
│
|
||||
├── 01-projects/ # Active projects
|
||||
│ ├── work/ # WORK PROJECTS (10 Basecamp projects)
|
||||
│ │ ├── _basecamp-activity.md # Basecamp sync log
|
||||
│ │ ├── _projects-index.md # Master index of all work projects
|
||||
│ │ │
|
||||
│ │ ├── project-a/ # [PROJECT NAME 1]
|
||||
│ │ │ ├── _index.md # Project MOC (links to Basecamp)
|
||||
│ │ │ ├── meetings/ # Teams meetings
|
||||
│ │ │ │ ├── standup-20260128.md
|
||||
│ │ │ │ └── planning-20260125.md
|
||||
│ │ │ │
|
||||
│ │ │ ├── decisions/ # Decision records
|
||||
│ │ │ │ ├── tech-stack-20260120.md
|
||||
│ │ │ │ └── feature-priority-20260115.md
|
||||
│ │ │ │
|
||||
│ │ │ ├── notes/ # Project notes
|
||||
│ │ │ │ ├── research-api.md
|
||||
│ │ │ │ └── design-ideas.md
|
||||
│ │ │ │
|
||||
│ │ │ └── basecamp-todos.md # Reference to Basecamp todos
|
||||
│ │ │
|
||||
│ │ ├── project-b/ # [PROJECT NAME 2]
|
||||
│ │ │ ├── _index.md
|
||||
│ │ │ ├── meetings/
|
||||
│ │ │ ├── decisions/
|
||||
│ │ │ ├── notes/
|
||||
│ │ │ └── basecamp-todos.md
|
||||
│ │ │
|
||||
│ │ ├── project-c/ # [PROJECT NAME 3]
|
||||
│ │ ├── project-d/ # [PROJECT NAME 4]
|
||||
│ │ ├── project-e/ # [PROJECT NAME 5]
|
||||
│ │ ├── project-f/ # [PROJECT NAME 6]
|
||||
│ │ ├── project-g/ # [PROJECT NAME 7]
|
||||
│ │ ├── project-h/ # [PROJECT NAME 8]
|
||||
│ │ ├── project-i/ # [PROJECT NAME 9]
|
||||
│ │ └── project-j/ # [PROJECT NAME 10]
|
||||
│ │
|
||||
│ └── personal/ # Personal projects
|
||||
│ ├── learn-rust/
|
||||
│ ├── home-office/
|
||||
│ └── fitness-challenge/
|
||||
│
|
||||
├── 02-areas/ # Ongoing responsibilities
|
||||
│ ├── work/ # Work areas
|
||||
│ │ ├── current-job.md # Current role and responsibilities
|
||||
│ │ ├── professional-dev.md # Learning goals, certifications
|
||||
│ │ ├── team-management.md # Team coordination, 1:1s
|
||||
│ │ ├── company-knowledge.md # Org-specific knowledge
|
||||
│ │ └── processes.md # SOPs, workflows
|
||||
│ │
|
||||
│ └── personal/ # Personal areas
|
||||
│ ├── health.md
|
||||
│ ├── finances.md
|
||||
│ ├── relationships.md
|
||||
│ ├── learning.md
|
||||
│ └── home.md
|
||||
│
|
||||
├── 03-resources/ # Reference material (tool-agnostic + tool-specific)
|
||||
│ ├── work/ # Work resources
|
||||
│ │ ├── wiki-mirror/ # Outline wiki exports (REPLACEABLE)
|
||||
│ │ │ ├── outline-api-guide.md
|
||||
│ │ │ ├── outline-deployment-sop.md
|
||||
│ │ │ ├── outline-monitoring.md
|
||||
│ │ │ └── _wiki-index.md # Master wiki index
|
||||
│ │ │
|
||||
│ │ ├── teams-archive/ # Teams recordings/notes (REPLACEABLE)
|
||||
│ │ │ └── _teams-index.md
|
||||
│ │ │
|
||||
│ │ ├── basecamp-references/ # Basecamp docs/guides (REPLACEABLE)
|
||||
│ │ │ └── _basecamp-docs.md
|
||||
│ │ │
|
||||
│ │ ├── company-procedures/ # SOPs, processes (KEEP)
|
||||
│ │ │ ├── code-review.md
|
||||
│ │ │ ├── deployment.md
|
||||
│ │ │ └── onboarding.md
|
||||
│ │ │
|
||||
│ │ ├── technical-stack/ # Tech documentation (KEEP)
|
||||
│ │ │ ├── backend.md
|
||||
│ │ │ ├── frontend.md
|
||||
│ │ │ └── infrastructure.md
|
||||
│ │ │
|
||||
│ │ └── _work-resources-index.md
|
||||
│ │
|
||||
│ └── personal/ # Personal resources
|
||||
│ ├── recipes.md
|
||||
│ ├── books.md
|
||||
│ └── travel.md
|
||||
│
|
||||
├── 04-archive/ # Completed/inactive
|
||||
│ ├── work/
|
||||
│ │ ├── old-job-2024/ # Archived employment
|
||||
│ │ └── projects/ # Completed projects
|
||||
│ │
|
||||
│ └── personal/
|
||||
│ └── projects/
|
||||
│
|
||||
├── daily/ # Daily notes
|
||||
│ ├── YYYY/
|
||||
│ │ └── MM/
|
||||
│ │ └── DD/
|
||||
│ │ └── YYYY-MM-DD.md
|
||||
│ └── weekly-reviews/
|
||||
│ └── YYYY-W##.md
|
||||
│
|
||||
└── tasks/ # Task management
|
||||
├── inbox.md # All incoming tasks
|
||||
├── recurring.md # Recurring tasks
|
||||
└── someday.md # Backlog items
|
||||
```
|
||||
|
||||
---
|
||||
title: "Work PARA Structure"
|
||||
type: index
|
||||
created: 2026-01-28
|
||||
---
|
||||
|
||||
## Work Project Template
|
||||
|
||||
Each of the 10 Basecamp projects should follow this structure:
|
||||
|
||||
### 1. Project _index.md (MOC)
|
||||
|
||||
```markdown
|
||||
---
|
||||
title: "[Project Name]"
|
||||
status: active | on-hold | completed
|
||||
deadline: YYYY-MM-DD
|
||||
priority: critical | high | medium | low
|
||||
source: basecamp
|
||||
basecamp_id: [BC_PROJECT_ID]
|
||||
basecamp_url: [BC_PROJECT_URL]
|
||||
tags: [work, basecamp, active]
|
||||
---
|
||||
|
||||
# [Project Name]
|
||||
# Work PARA Structure
|
||||
|
||||
## Overview
|
||||
[Brief description of project goals and scope]
|
||||
PARA structure for work-related projects, areas, and resources. Designed for tool-agnostic knowledge management.
|
||||
|
||||
## Basecamp Link
|
||||
[View in Basecamp](basecamp_url)
|
||||
## Directory Tree
|
||||
|
||||
## Related Areas
|
||||
- [[current-job]]
|
||||
- [[team-management]]
|
||||
|
||||
## Resources
|
||||
- [[outline-api-guide]]
|
||||
- [[technical-stack-backend]]
|
||||
|
||||
## Quick Links
|
||||
- [ ] Basecamp Todos
|
||||
- [ ] Basecamp Messages
|
||||
- [ ] Teams Channel
|
||||
- [ ] Wiki Documentation
|
||||
|
||||
## Notes
|
||||
- [ ] Latest update (YYYY-MM-DD): [Summary]
|
||||
- [ ] Latest update (YYYY-MM-DD): [Summary]
|
||||
|
||||
## Sub-Projects/Milestones
|
||||
- [ ] Milestone 1
|
||||
- [ ] Milestone 2
|
||||
- [ ] Milestone 3
|
||||
```
|
||||
|
||||
### 2. meetings/ folder
|
||||
|
||||
Naming pattern: `[type]-YYYYMMDD.md`
|
||||
|
||||
Example: `standup-20260128.md`, `planning-20260125.md`, `review-20260120.md`
|
||||
|
||||
### 3. decisions/ folder
|
||||
|
||||
Naming pattern: `[topic]-YYYYMMDD.md`
|
||||
|
||||
Example: `tech-stack-choice-20260120.md`, `feature-priority-20260115.md`
|
||||
|
||||
### 4. notes/ folder
|
||||
|
||||
Free-form project notes. Organize by topic or date.
|
||||
|
||||
Example: `research-api.md`, `design-ideas.md`, `bug-analysis.md`
|
||||
|
||||
---
|
||||
|
||||
## Tool-Specific vs Tool-Agnostic Folders
|
||||
|
||||
### Keep These (Tool-Agnostic)
|
||||
```
|
||||
~/CODEX/
|
||||
├── 02-areas/work/ # Job-specific knowledge (stays with you)
|
||||
├── 03-resources/work/
|
||||
│ ├── company-procedures/ # Your documented processes
|
||||
│ ├── technical-stack/ # Tech knowledge
|
||||
│ └── learnings/ # What you learned
|
||||
└── 01-projects/work/ # Project structure (stays)
|
||||
├── 01-projects/work/ # Active work projects
|
||||
│ ├── api-integration-platform/
|
||||
│ │ ├── _index.md
|
||||
│ │ ├── meetings/
|
||||
│ │ ├── decisions/
|
||||
│ │ └── notes/
|
||||
│ ├── customer-portal-redesign/
|
||||
│ │ └── (same structure)
|
||||
│ ├── marketing-campaign-q1/
|
||||
│ ├── security-audit-2026/
|
||||
│ ├── infrastructure-migration/
|
||||
│ ├── mobile-app-v20/
|
||||
│ ├── team-onboarding-program/
|
||||
│ ├── data-analytics-dashboard/
|
||||
│ ├── documentation-revamp/
|
||||
│ └── api-gateway-upgrade/
|
||||
│
|
||||
├── 02-areas/work/ # Ongoing work responsibilities
|
||||
│ ├── current-job.md
|
||||
│ ├── professional-dev.md
|
||||
│ ├── team-management.md
|
||||
│ ├── company-knowledge.md
|
||||
│ └── technical-excellence.md
|
||||
│
|
||||
├── 03-resources/work/ # Work reference material
|
||||
│ └── wiki-mirror/ # Outline wiki exports
|
||||
│ └── _wiki-index.md
|
||||
│
|
||||
└── 04-archive/work/ # Completed work
|
||||
├── projects/ # Finished projects
|
||||
└── employment/ # Job transitions
|
||||
```
|
||||
|
||||
### Replace These (Tool-Specific)
|
||||
## Project Mapping
|
||||
|
||||
| Basecamp Project | PARA Path | Type | Status | Deadline |
|
||||
|----------------|-----------|-------|---------|-----------|
|
||||
| API Integration Platform | `01-projects/work/api-integration-platform` | Engineering | Active | 2026-03-15 |
|
||||
| Customer Portal Redesign | `01-projects/work/customer-portal-redesign` | Product/Design | Active | 2026-04-30 |
|
||||
| Marketing Campaign Q1 | `01-projects/work/marketing-campaign-q1` | Marketing | Active | 2026-02-28 |
|
||||
| Security Audit 2026 | `01-projects/work/security-audit-2026` | Security | Active | 2026-03-31 |
|
||||
| Infrastructure Migration | `01-projects/work/infrastructure-migration` | Operations | Active | 2026-06-30 |
|
||||
| Mobile App v2.0 | `01-projects/work/mobile-app-v20` | Product | On Hold | 2026-05-15 |
|
||||
| Team Onboarding Program | `01-projects/work/team-onboarding-program` | HR/Operations | Active | 2026-02-15 |
|
||||
| Data Analytics Dashboard | `01-projects/work/data-analytics-dashboard` | Engineering | Active | 2026-04-15 |
|
||||
| Documentation Revamp | `01-projects/work/documentation-revamp` | Documentation | Active | 2026-03-30 |
|
||||
| API Gateway Upgrade | `01-projects/work/api-gateway-upgrade` | Engineering | On Hold | 2026-07-31 |
|
||||
|
||||
## Integration Points
|
||||
|
||||
### Basecamp Integration
|
||||
- **Skill**: `basecamp` (MCP)
|
||||
- **Mapping**: See Basecamp project IDs → PARA paths
|
||||
- **Sync**: Manual sync via skill or future n8n automation
|
||||
- **Status Check**: "What's in [project]?" → Basecamp
|
||||
|
||||
### Outline Wiki Integration
|
||||
- **Skill**: `outline` (MCP)
|
||||
- **Live Search**: "Search Outline for [topic]"
|
||||
- **Export**: "Export [document] to Obsidian"
|
||||
- **Location**: `03-resources/work/wiki-mirror/`
|
||||
|
||||
### Teams Meeting Integration
|
||||
- **Skill**: `meeting-notes`
|
||||
- **Workflow**: DOCX → AI analysis → meeting note → Basecamp sync
|
||||
- **Location**: `01-projects/work/[project]/meetings/`
|
||||
- **Guide**: See `skills/meeting-notes/references/teams-transcript-workflow.md`
|
||||
|
||||
## Workflows
|
||||
|
||||
### Morning Planning with Work Context
|
||||
```
|
||||
~/CODEX/03-resources/work/
|
||||
├── wiki-mirror/ # Delete when switching jobs (Outline)
|
||||
├── teams-archive/ # Delete when switching jobs (Teams)
|
||||
├── basecamp-references/ # Delete when switching jobs (Basecamp)
|
||||
└── [other-tools]/ # Delete when switching jobs
|
||||
1. Read yesterday's daily note
|
||||
2. Check Basecamp: "Show my Basecamp todos due today"
|
||||
3. Check Outline: "Search Outline for [project topic]"
|
||||
4. Create integrated morning plan with:
|
||||
- Work priorities (from Basecamp)
|
||||
- Personal priorities (from PARA)
|
||||
- Meeting schedule
|
||||
- Deep work blocks
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Master Index Files
|
||||
|
||||
### _projects-index.md
|
||||
|
||||
```markdown
|
||||
# Work Projects Index
|
||||
|
||||
Last updated: YYYY-MM-DD
|
||||
|
||||
## Active Projects (10 total)
|
||||
|
||||
| Project | Status | Deadline | Priority | Basecamp |
|
||||
|---------|--------|-----------|-----------|-----------|
|
||||
| [[project-a]] | Active | 2026-03-15 | High | [Link] |
|
||||
| [[project-b]] | On Hold | 2026-04-01 | Medium | [Link] |
|
||||
| [[project-c]] | Active | 2026-02-28 | Critical | [Link] |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
## By Priority
|
||||
|
||||
### Critical (2 projects)
|
||||
- [[project-c]]
|
||||
- [[project-g]]
|
||||
|
||||
### High (5 projects)
|
||||
- [[project-a]]
|
||||
- [[project-d]]
|
||||
- [[project-f]]
|
||||
- [[project-h]]
|
||||
- [[project-j]]
|
||||
|
||||
### Medium (3 projects)
|
||||
- [[project-b]]
|
||||
- [[project-e]]
|
||||
- [[project-i]]
|
||||
|
||||
## By Deadline
|
||||
|
||||
### Due This Week
|
||||
- [[project-a]] (2026-02-01)
|
||||
|
||||
### Due Next Week
|
||||
- [[project-c]] (2026-03-15)
|
||||
|
||||
### Due This Month
|
||||
- [[project-b]] (2026-04-01)
|
||||
### Evening Reflection with Work Context
|
||||
```
|
||||
1. Review completed Basecamp tasks
|
||||
2. Review project progress
|
||||
3. Capture work learnings
|
||||
4. Export decisions to Outline (if applicable)
|
||||
5. Plan tomorrow's work priorities
|
||||
```
|
||||
|
||||
### _basecamp-activity.md
|
||||
|
||||
```markdown
|
||||
# Basecamp Activity Log
|
||||
|
||||
Last sync: YYYY-MM-DD HH:mm
|
||||
|
||||
## Today (YYYY-MM-DD)
|
||||
- [10:30] Created todo: "Implement feature X" in project-a
|
||||
- [11:45] Completed todo: "Review PR #123" in project-c
|
||||
- [14:00] Comment added to "API Design" message in project-a
|
||||
|
||||
## Yesterday (YYYY-MM-DD)
|
||||
- [09:00] Created card: "Bug fix investigation" in project-b
|
||||
- [16:30] Completed todo: "Update documentation" in project-g
|
||||
|
||||
## This Week
|
||||
- Total todos created: 23
|
||||
- Total todos completed: 18
|
||||
- Total messages: 5
|
||||
- Active projects: 10
|
||||
|
||||
## Quick Stats
|
||||
- Project with most activity: [[project-a]] (8 items)
|
||||
- Overdue todos: 3
|
||||
- Cards in review: 5
|
||||
### Weekly Review with Work
|
||||
```
|
||||
1. Check all Basecamp project status
|
||||
2. Review work area health
|
||||
3. Identify at-risk projects
|
||||
4. Plan next week's priorities
|
||||
5. Process work inbox
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Migration Guide (Job Switch)
|
||||
## Job Transition Checklist
|
||||
|
||||
When switching jobs:
|
||||
|
||||
### Step 1: Archive Current Work
|
||||
```bash
|
||||
# Move entire work structure to archive
|
||||
mv ~/CODEX/01-projects/work/ ~/CODEX/04-archive/work/old-job-2024/
|
||||
1. **Archive Current Work**:
|
||||
- Move `01-projects/work/` → `04-archive/work/[old-company]/`
|
||||
- Move `02-areas/work/` → `04-archive/work/[old-company]/`
|
||||
- Keep `03-resources/work/wiki-mirror/` (company knowledge)
|
||||
|
||||
# Archive work areas (optional, if job-specific)
|
||||
mv ~/CODEX/02-areas/work/ ~/CODEX/04-archive/work/areas-old-job/
|
||||
2. **Update Tool Configurations**:
|
||||
- Basecamp: Remove old projects, add new ones
|
||||
- Outline: Update collections (if switching wikis)
|
||||
- Keep work structure intact
|
||||
|
||||
# Archive tool-specific resources
|
||||
rm -rf ~/CODEX/03-resources/work/wiki-mirror/
|
||||
rm -rf ~/CODEX/03-resources/work/teams-archive/
|
||||
rm -rf ~/CODEX/03-resources/work/basecamp-references/
|
||||
```
|
||||
3. **Create New Work Structure**:
|
||||
- Create new `01-projects/work/` folders
|
||||
- Update `02-areas/work/` areas
|
||||
- Preserve PARA methodology
|
||||
|
||||
### Step 2: Clean Areas (Keep What's Generic)
|
||||
```bash
|
||||
# Keep professional-dev.md (generic learning)
|
||||
# Keep processes.md (if generic)
|
||||
# Delete job-specific files in 02-areas/work/
|
||||
rm ~/CODEX/02-areas/work/current-job.md
|
||||
rm ~/CODEX/02-areas/work/team-management.md
|
||||
rm ~/CODEX/02-areas/work/company-knowledge.md
|
||||
```
|
||||
## Quick Commands
|
||||
|
||||
### Step 3: Set Up New Job
|
||||
```bash
|
||||
# Create new work project structure
|
||||
mkdir -p ~/CODEX/01-projects/work/
|
||||
mkdir -p ~/CODEX/01-projects/work/_basecamp-activity.md
|
||||
mkdir -p ~/CODEX/01-projects/work/_projects-index.md
|
||||
| Action | Command |
|
||||
|--------|----------|
|
||||
| Start work day | "/chiron-start" → morning planning with Basecamp |
|
||||
| End work day | "/chiron-end" → reflection with work metrics |
|
||||
| Weekly review | "/chiron-review" → work project status review |
|
||||
| Check Basecamp | "Show my Basecamp projects" or "What's in [project]?" |
|
||||
| Search wiki | "Search Outline for [topic]" |
|
||||
| Process meeting | "Process transcript: [file.docx]" |
|
||||
| Project status | "What's status of [project name]?" |
|
||||
|
||||
# Create new work areas
|
||||
echo "---\ntitle: \"Current Job\"\nstatus: active\n---\n# Current Job\n\n## Role\n[Your role]\n\n## Responsibilities\n- [Responsibility 1]\n- [Responsibility 2]\n" > ~/CODEX/02-areas/work/current-job.md
|
||||
## Notes
|
||||
|
||||
# Set up new tool folders
|
||||
mkdir -p ~/CODEX/03-resources/work/wiki-mirror/
|
||||
mkdir -p ~/CODEX/03-resources/work/teams-archive/
|
||||
mkdir -p ~/CODEX/03-resources/work/basecamp-references/
|
||||
```
|
||||
|
||||
### Step 4: Import Basecamp Projects
|
||||
Use `basecamp` skill:
|
||||
```
|
||||
User: "Show my Basecamp projects"
|
||||
# Review 10 projects
|
||||
|
||||
User: "Create project notes for all Basecamp projects"
|
||||
# Generates _index.md for each project
|
||||
# Populates _projects-index.md
|
||||
```
|
||||
|
||||
### Step 5: Configure n8n Workflows
|
||||
- Update Basecamp webhook URLs
|
||||
- Configure Outline API for new job
|
||||
- Update Teams transcript webhook
|
||||
- Test all automations
|
||||
- All work knowledge stored in Obsidian (tool-agnostic)
|
||||
- Basecamp used for real-time task tracking
|
||||
- Outline used for live wiki access
|
||||
- Teams transcripts processed with AI analysis
|
||||
- n8n automation ready for future implementation
|
||||
|
||||
---
|
||||
|
||||
## Implementation Checklist
|
||||
|
||||
### Initial Setup (One-time)
|
||||
- [ ] Create directory structure in ~/CODEX/
|
||||
- [ ] Create _projects-index.md template
|
||||
- [ ] Create _basecamp-activity.md
|
||||
- [ ] Configure basecamp skill with project IDs
|
||||
- [ ] Set up n8n workflows
|
||||
- [ ] Configure Outline MCP server
|
||||
- [ ] Create meeting-transcript.md template
|
||||
|
||||
### Ongoing Maintenance
|
||||
- [ ] Weekly: Review project status and update _projects-index.md
|
||||
- [ ] Weekly: Archive completed projects to 04-archive/
|
||||
- [ ] Weekly: Process inbox items
|
||||
- [ ] Weekly: Review _basecamp-activity.md
|
||||
- [ ] Monthly: Review 02-areas/work/ health
|
||||
|
||||
### Job Switch (When needed)
|
||||
- [ ] Archive 01-projects/work/ to 04-archive/work/
|
||||
- [ ] Archive tool-specific resources (wiki-mirror, teams-archive, basecamp-references/)
|
||||
- [ ] Clean up job-specific areas
|
||||
- [ ] Set up new project structure
|
||||
- [ ] Import new Basecamp projects
|
||||
- [ ] Configure new tool integrations
|
||||
**Last updated**: 2026-01-28
|
||||
|
||||
374
skills/chiron-core/references/work-quickstart.md
Normal file
374
skills/chiron-core/references/work-quickstart.md
Normal file
@@ -0,0 +1,374 @@
|
||||
# Work Integration Quick Start Guide
|
||||
|
||||
Quick reference for using your work integration with Basecamp, Outline, and Teams.
|
||||
|
||||
## 🚀 First-Time Setup
|
||||
|
||||
### 1. Customize Your Projects
|
||||
|
||||
The 10 projects in `01-projects/work/` are placeholders. Customize them:
|
||||
|
||||
```bash
|
||||
# Option A: Fetch from Basecamp (when MCP is ready)
|
||||
"Show my Basecamp projects" → Get actual project names
|
||||
|
||||
# Option B: Manual customization
|
||||
cd ~/CODEX/01-projects/work
|
||||
# Rename folders to match your actual Basecamp projects
|
||||
# Update each _index.md with:
|
||||
# - Correct project name
|
||||
# - Actual Basecamp project ID
|
||||
# - Real deadline
|
||||
# - Actual status
|
||||
```
|
||||
|
||||
### 2. Set Up Outline MCP
|
||||
|
||||
```bash
|
||||
# Install Outline MCP server
|
||||
pip install mcp-outline
|
||||
|
||||
# Configure in your Opencode/MCP client
|
||||
# See: https://github.com/Vortiago/mcp-outline
|
||||
# Set OUTLINE_API_KEY and OUTLINE_API_URL
|
||||
```
|
||||
|
||||
### 3. Test Basecamp Connection
|
||||
|
||||
```bash
|
||||
# Test Basecamp MCP
|
||||
"Show my Basecamp projects"
|
||||
|
||||
# Should list your actual projects
|
||||
# If successful, ready to use
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📅 Daily Work Workflow
|
||||
|
||||
### Morning Planning
|
||||
|
||||
```
|
||||
"Start day" or "/chiron-start"
|
||||
```
|
||||
|
||||
**What happens**:
|
||||
1. Checks yesterday's completed tasks
|
||||
2. Fetches today's Basecamp todos
|
||||
3. Searches Outline for relevant wiki docs
|
||||
4. Creates integrated morning plan
|
||||
|
||||
**Output includes**:
|
||||
- Work priorities (from Basecamp)
|
||||
- Personal priorities (from PARA areas)
|
||||
- Meeting schedule
|
||||
- Deep work blocks protected
|
||||
|
||||
### During Work Day
|
||||
|
||||
**Check Basecamp status**:
|
||||
```bash
|
||||
"What's in API Integration Platform?"
|
||||
"Show my Basecamp todos due today"
|
||||
"Search Basecamp for OAuth2"
|
||||
```
|
||||
|
||||
**Search wiki for context**:
|
||||
```bash
|
||||
"Search Outline for authentication best practices"
|
||||
"Search Outline for API rate limiting"
|
||||
```
|
||||
|
||||
**Quick capture**:
|
||||
```bash
|
||||
"Capture: OAuth2 needs refresh token logic"
|
||||
# → Saved to 00-inbox/work/
|
||||
```
|
||||
|
||||
**Process meeting transcript**:
|
||||
```bash
|
||||
"Process transcript: api-design-review.docx"
|
||||
# → Creates meeting note
|
||||
# → Extracts action items
|
||||
# → Optionally syncs to Basecamp
|
||||
```
|
||||
|
||||
### Evening Reflection
|
||||
|
||||
```
|
||||
"End day" or "/chiron-end"
|
||||
```
|
||||
|
||||
**What happens**:
|
||||
1. Reviews completed Basecamp tasks
|
||||
2. Captures work wins and learnings
|
||||
3. Checks project progress
|
||||
4. Plans tomorrow's work priorities
|
||||
5. Updates work metrics
|
||||
|
||||
---
|
||||
|
||||
## 📊 Weekly Work Review
|
||||
|
||||
```
|
||||
"Weekly review" or "/chiron-review"
|
||||
```
|
||||
|
||||
**What happens**:
|
||||
1. Checks all Basecamp project status (completion %, overdue items)
|
||||
2. Reviews work area health
|
||||
3. Identifies at-risk projects
|
||||
4. Plans next week's work priorities
|
||||
5. Processes work inbox
|
||||
|
||||
**Output includes**:
|
||||
- Work metrics (tasks completed, projects progressed)
|
||||
- Work wins and challenges
|
||||
- Project status overview (on track, behind, at risk)
|
||||
- Work area health review
|
||||
- Next week's priorities
|
||||
|
||||
---
|
||||
|
||||
## 🔧 Tool-Specific Commands
|
||||
|
||||
### Basecamp (Project Management)
|
||||
|
||||
**List all projects**:
|
||||
```bash
|
||||
"Show my Basecamp projects"
|
||||
```
|
||||
|
||||
**Check project status**:
|
||||
```bash
|
||||
"What's in API Integration Platform?"
|
||||
"What's status of Customer Portal Redesign?"
|
||||
```
|
||||
|
||||
**Create todos**:
|
||||
```bash
|
||||
"Add todos to API Integration Platform"
|
||||
# → Prompts for: project, todo list, tasks with due dates
|
||||
```
|
||||
|
||||
**Search content**:
|
||||
```bash
|
||||
"Search Basecamp for OAuth2"
|
||||
```
|
||||
|
||||
### Outline (Wiki Knowledge)
|
||||
|
||||
**Search wiki**:
|
||||
```bash
|
||||
"Search Outline for API authentication"
|
||||
"Ask Outline: How do we handle rate limiting?"
|
||||
```
|
||||
|
||||
**Read document**:
|
||||
```bash
|
||||
"Show me OAuth2 Setup Guide"
|
||||
```
|
||||
|
||||
**Export to Obsidian**:
|
||||
```bash
|
||||
"Export OAuth2 Setup Guide to Obsidian"
|
||||
# → Saves to 03-resources/work/wiki-mirror/
|
||||
# → Adds frontmatter with outline source
|
||||
# → Links to related projects/areas
|
||||
```
|
||||
|
||||
**Create wiki document**:
|
||||
```bash
|
||||
"Create Outline doc: API Authentication Decision"
|
||||
# → Creates in Outline with provided content
|
||||
# → Adds to appropriate collection
|
||||
```
|
||||
|
||||
### Teams (Meetings)
|
||||
|
||||
**Process transcript**:
|
||||
```bash
|
||||
"Process transcript: [filename.docx]"
|
||||
```
|
||||
|
||||
**Workflow**:
|
||||
1. Upload transcript file
|
||||
2. Extract text from DOCX
|
||||
3. AI analysis extracts: attendees, topics, decisions, action items
|
||||
4. Creates meeting note in Obsidian
|
||||
5. Optionally syncs action items to Basecamp
|
||||
|
||||
**Manual steps** (see `skills/meeting-notes/references/teams-transcript-workflow.md`):
|
||||
```bash
|
||||
# Step 1: Download transcript from Teams
|
||||
# Step 2: Extract text
|
||||
python extract_transcript.py transcript.docx
|
||||
|
||||
# Step 3: Ask AI to analyze
|
||||
# (Paste transcript into AI prompt from workflow guide)
|
||||
|
||||
# Step 4: Create meeting note using meeting-notes skill
|
||||
|
||||
# Step 5 (Optional): Sync action items to Basecamp
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Quick Reference
|
||||
|
||||
| I Want To... | Command | Tool |
|
||||
|----------------|----------|-------|
|
||||
| See today's work | "/chiron-start" | Morning planning |
|
||||
| Review my day | "/chiron-end" | Evening reflection |
|
||||
| See project status | "What's in [project]?" | Basecamp |
|
||||
| Find wiki info | "Search Outline for [topic]" | Outline |
|
||||
| Process meeting | "Process transcript: [file]" | Teams + AI |
|
||||
| Weekly review | "/chiron-review" | Weekly review |
|
||||
| Create wiki doc | "Create Outline doc: [title]" | Outline |
|
||||
| Export wiki doc | "Export [doc] to Obsidian" | Outline |
|
||||
| Quick capture | "Capture: [thought]" | Quick capture |
|
||||
|
||||
---
|
||||
|
||||
## 🔗 Integration Examples
|
||||
|
||||
### Example 1: Starting a New Project
|
||||
|
||||
```bash
|
||||
# 1. Create project in PARA (manually or from plan-writing)
|
||||
# 2. Create project folder in 01-projects/work/
|
||||
# 3. Link to Basecamp (if project exists there)
|
||||
|
||||
User: "What's the status of API Integration Platform in Basecamp?"
|
||||
→ Gets: 65% complete, next milestone: OAuth2 endpoints
|
||||
|
||||
User: "Search Outline for OAuth2 setup guides"
|
||||
→ Gets: 3 relevant documents
|
||||
|
||||
User: "Export OAuth2 Setup Guide to Obsidian"
|
||||
→ Saves to project/notes/oauth2-setup-guide.md
|
||||
→ Links from project MOC
|
||||
```
|
||||
|
||||
### Example 2: Processing a Meeting
|
||||
|
||||
```bash
|
||||
User: "Process transcript: api-design-review.docx"
|
||||
|
||||
System:
|
||||
1. Extracts text from DOCX
|
||||
2. AI analyzes: attendees, topics, decisions, action items
|
||||
3. Creates meeting note: 01-projects/work/api-integration-platform/meetings/api-design-review-20260128.md
|
||||
4. Outputs action items:
|
||||
- [ ] Create OAuth2 implementation guide #meeting #todo 🔼 👤 @alice 📅 2026-02-05
|
||||
- [ ] Document rate limiting policy #meeting #todo 🔼 👤 @bob 📅 2026-02-10
|
||||
|
||||
User: "Sync action items to Basecamp?"
|
||||
→ System creates 2 todos in API Integration Platform project
|
||||
→ Assigns to Alice and Bob
|
||||
→ Sets due dates
|
||||
```
|
||||
|
||||
### Example 3: Daily Work Flow
|
||||
|
||||
```bash
|
||||
Morning:
|
||||
"/chiron-start"
|
||||
→ Gets: 5 Basecamp todos due today
|
||||
→ Gets: 2 meetings scheduled
|
||||
→ Searches Outline: "API authentication patterns"
|
||||
→ Creates integrated plan:
|
||||
- Work: Complete OAuth2 flow (P0)
|
||||
- Work: Review dashboard mockups (P1)
|
||||
- Meeting: Architecture review (2pm)
|
||||
- Deep work: 9-11am (OAuth2)
|
||||
|
||||
During work:
|
||||
"Search Basecamp for OAuth2"
|
||||
→ Finds: 3 docs, 2 todos
|
||||
|
||||
Evening:
|
||||
"/chiron-end"
|
||||
→ Reviews: OAuth2 flow complete
|
||||
→ Captures: Learning about token refresh pattern
|
||||
→ Checks project: 70% complete now
|
||||
→ Plans: Tomorrow: Finish API endpoints
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 Best Practices
|
||||
|
||||
### Daily Use
|
||||
1. **Start with morning plan** - Sets focus for the day
|
||||
2. **Check Basecamp first** - Prioritize work tasks
|
||||
3. **Search Outline for context** - Get knowledge before starting
|
||||
4. **Quick capture interruptions** - Don't break flow, capture and continue
|
||||
5. **End with evening reflection** - Review and plan tomorrow
|
||||
|
||||
### Weekly Use
|
||||
1. **Dedicated time** - 60-90 minutes for weekly review
|
||||
2. **Check all projects** - Don't forget any
|
||||
3. **Review area health** - Balance attention across responsibilities
|
||||
4. **Process inbox** - Keep 00-inbox/ clean
|
||||
5. **Plan next week** - Set priorities, don't just review
|
||||
|
||||
### Tool Use
|
||||
1. **Basecamp for tasks** - Live task tracking
|
||||
2. **Outline for knowledge** - Persistent wiki access
|
||||
3. **Obsidian for storage** - Tool-agnostic knowledge
|
||||
4. **Teams transcripts** - Process within 24 hours
|
||||
5. **AI for analysis** - Extract insights from transcripts/docs
|
||||
|
||||
---
|
||||
|
||||
## 🔧 Troubleshooting
|
||||
|
||||
### Basecamp MCP Not Working
|
||||
**Check**:
|
||||
- MCP server running?
|
||||
- API key configured?
|
||||
- Connection to Basecamp?
|
||||
|
||||
### Outline MCP Not Working
|
||||
**Check**:
|
||||
- `pip install mcp-outline` completed?
|
||||
- OUTLINE_API_KEY set?
|
||||
- OUTLINE_API_URL correct?
|
||||
|
||||
### Project Not Found in Basecamp
|
||||
**Check**:
|
||||
- Project name matches exactly?
|
||||
- Project in correct workspace?
|
||||
|
||||
### Wiki Search No Results
|
||||
**Try**:
|
||||
- Broader query (fewer keywords)
|
||||
- Remove collection_id to search everywhere
|
||||
- Use `ask_ai_about_documents` for semantic search
|
||||
|
||||
### Transcript Processing Fails
|
||||
**Check**:
|
||||
- DOCX file valid?
|
||||
- `python-docx` installed?
|
||||
- AI prompt clear enough?
|
||||
|
||||
---
|
||||
|
||||
## 📚 Documentation Links
|
||||
|
||||
For detailed guides, see:
|
||||
|
||||
- **PARA Work Structure**: `skills/chiron-core/references/work-para-structure.md`
|
||||
- **Basecamp Skill**: `skills/basecamp/SKILL.md`
|
||||
- **Outline Skill**: `skills/outline/SKILL.md`
|
||||
- **Daily Routines**: `skills/daily-routines/SKILL.md`
|
||||
- **Meeting Notes**: `skills/meeting-notes/SKILL.md`
|
||||
- **Teams Transcript Workflow**: `skills/meeting-notes/references/teams-transcript-workflow.md`
|
||||
- **Outline Workflows**: `skills/outline/references/outline-workflows.md`
|
||||
- **Export Patterns**: `skills/outline/references/export-patterns.md`
|
||||
|
||||
---
|
||||
|
||||
**Last updated**: 2026-01-28
|
||||
Reference in New Issue
Block a user