### Full Report Example Source: https://github.com/borisvu/obsidian-vault-cowork-plugins/blob/master/para-flow/commands/standup.md An example output of the full daily report, including sections for 'What I worked on' and 'Plan for next work day'. ```markdown ## Daily Report — 2026-02-09 (Sunday) ### What I worked on - Prepared for a sync with John tomorrow. - Worked on a production issue — Audit operation ended without results (PROJECT-7292). ### Plan for next work day (Monday, 2026-02-10) - [items from "To do on the next working day" section] ``` -------------------------------- ### Standup Report Example (Default) Source: https://github.com/borisvu/obsidian-vault-cowork-plugins/blob/master/para-flow/commands/standup.md An example output of the default laconic standup report, showing tasks completed and planned tasks. ```markdown Tasks completed since last report: Thursday: • Merged PROJECT-7371 • Sync with John on API design • Reviewed pull request for auth module Will do today: • Continue PROJECT-7292 investigation • Prepare demo for sprint review ``` -------------------------------- ### Memory Lookup Flow Example Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Details the sequence of steps involved in looking up information for a user query, starting with the CLAUDE.md hot cache and progressing to PARA folders and external Jira lookups if necessary. It shows how a query is decoded into a comprehensive answer. ```markdown User input: "ask john about the audit issue on project-7292" Lookup sequence: 1. Check CLAUDE.md (hot cache) → john? ✓ John Smith, CTO → project-7292? Not in hot cache 2. Check PARA (deep storage) → Search PARA/1 Projects/*/ for PROJECT-7292 → Glob: PARA/1 Projects/*/PROJECT-7292* or PARA/1 Projects/PROJECT-7292* → Found: PARA/1 Projects/PROJECT-7292 - Audit operation ended without results/ ✓ 3. If not found → check Jira via MCP → Query Atlassian MCP for ticket details → Create vault note, add to CLAUDE.md if relevant 4. If nothing → ask user → "What is PROJECT-7292? I'll remember it." Decoded output: "Ask John Smith (CTO) about the audit operation failure on PROJECT-7292 (Audit operation ended without results, P1 bug)" ``` -------------------------------- ### Standup Command Usage Examples Source: https://github.com/borisvu/obsidian-vault-cowork-plugins/blob/master/para-flow/commands/standup.md Demonstrates various ways to invoke the standup command, including default laconic standup, full comprehensive report, and filtering by a specific date range. ```shell /para-flow:standup → laconic standup (default) /para-flow:standup --full → comprehensive daily report /para-flow:standup since 2026-02-06 → standup format, date range /para-flow:standup --full since 2026-02-06 → full format, date range ``` -------------------------------- ### CLAUDE.md Structure for Hot Cache Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Defines the structure of CLAUDE.md, which serves as a hot cache for frequently accessed information. It includes sections for Memory, People, Terms, Projects, and Preferences, with examples of how data is organized. ```markdown # CLAUDE.md Structure (Hot Cache - ~50-80 lines) # Memory ## Me [Name], [Role] on [Team]. [One sentence.] ## People | Who | Role | | --------- | ---------------------------------- | | **John** | John Smith, CTO | | **Sarah** | Sarah Chen, Engineering (Platform) | > Full profiles: PARA/2 Areas/People/ ## Terms | Term | Meaning | | ---- | ------------------------ | | PSR | Pipeline Status Report | | P0 | Drop everything priority | > Full glossary: PARA/3 Resources/Terms/ ## Projects | Name | What | | ---------------- | ----------------------- | | **PROJECT-7292** | Audit operation bug, P1 | | **Phoenix** | DB migration, Q2 launch | > Details: PARA/1 Projects/ ## Preferences - Work week: Sun-Thu (Israel) - Async-first communication - PARA method for organization - Obsidian for knowledge management ``` -------------------------------- ### Initialize Para Flow System Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Initializes the task and memory systems within an existing PARA-based Obsidian vault. It creates the CLAUDE.md file if missing and bootstraps memory from existing vault content. ```bash /para-flow:start ``` -------------------------------- ### Manage Project Lifecycle Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Scans the PARA/1 Projects/ directory for stale projects based on a configurable staleness threshold. It classifies projects for archiving and provides a summary of moves to the archive folder. ```bash /para-flow:archive ``` -------------------------------- ### Generate Daily Standup Reports Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Generates standup summaries or full daily reports based on Work Diary entries. It supports laconic, full, and multi-day reporting formats by resolving Obsidian links and cleaning tags. ```bash /para-flow:standup /para-flow:standup --full /para-flow:standup since 2026-02-06 /para-flow:standup --full since 2026-02-06 ``` -------------------------------- ### Daily Note Template Structure Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt A Markdown template for daily work logging. It includes sections for goals, tasks completed, achievements, and future planning, utilizing Obsidian's wiki-link syntax for cross-referencing. ```markdown # Daily Note Template (Work Diary/YYYY/MM/YYYY-MM-DD.md) --- tags: - Daily_Report --- # Goals - [ ] Review PR for auth module - [ ] Complete API documentation # Worked on today - Sync with [[John Smith|John]] about [[PROJECT-7292]] - Fixed regression in audit flow #unplanned - Code review for auth module PR # Achievements - Merged [[PROJECT-7371]] after 3-week effort # To do on the next working day - Continue PROJECT-7292 investigation - Prepare demo for sprint review # Free notes Personal notes and informal content here... ``` -------------------------------- ### Define Obsidian YAML Frontmatter Template Source: https://github.com/borisvu/obsidian-vault-cowork-plugins/blob/master/para-flow/skills/memory-management/SKILL.md A standard YAML frontmatter template required for all new files created within the Obsidian vault to ensure consistent metadata tracking and tagging. ```yaml --- aliases: - { short name or alternate reference } tags: - { relevant tags as YAML array } creation_date: { YYYY-MM-DD } last_updated: { YYYY-MM-DD } --- ``` -------------------------------- ### Archive Projects with /para-flow:archive Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Archives projects based on a specified staleness threshold. It takes a number of days as input and outputs a summary of archived projects. ```bash # Custom staleness threshold (90 days) /para-flow:archive --since 90 # Post-archive summary: # Archived 2 projects: # PROJECT-7371 - Sync fails → Archive 2026/PROJECT-7371 - Sync fails/ # PROJECT-7457 - Stuck definitions → Archive 2026/PROJECT-7457 - Stuck definitions/ ``` -------------------------------- ### PARA Folder Structure Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Illustrates the PARA (Projects, Areas, Resources, Archive) folder structure used for organizing information within the Obsidian vault. Each top-level folder has a specific purpose for categorizing notes and projects. ```markdown PARA/ ├── 0 Inbox/ ← Unsorted items ├── 1 Projects/ ← Active project folders │ ├── {Project Name}/ ← Subdirectory per project │ └── {KEY} - {Summary}/ ← Jira tickets assigned to you ├── 2 Areas/ │ ├── People/ ← Individual people profiles │ ├── Partners/ ← Partner company profiles │ └── Customers/ ← Customer company profiles ├── 3 Resources/ │ ├── Terms/ ← Individual term/acronym files │ ├── Jira/ ← Jira tickets not assigned to you │ └── Company/ ← Company context, teams, processes └── 4 Archive/ ← Completed projects (by year) └── Archive {YYYY}/ ``` -------------------------------- ### Sync Tasks and Refresh Memory Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Synchronizes Jira tasks, triages stale items, and identifies memory gaps. The comprehensive mode performs a deep scan of the vault to suggest new people and terms based on frequency and context. ```bash /para-flow:update /para-flow:update --comprehensive ``` -------------------------------- ### Jira Link Resolution Logic Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Defines the pattern matching and resolution flow for Jira tickets within the vault. It describes how the system searches local files before querying the Atlassian MCP and formatting the output based on the user's current mode. ```markdown # Automatic Jira link detection patterns: [[PROJECT-7292]] → Detected as Jira ticket [[IDEA-123]] → Detected as Jira ticket [[UPPERCASE-DIGITS]] → Generic Jira pattern # Resolution flow: 1. Search vault: PARA/1 Projects/*/{KEY}* and PARA/3 Resources/Jira/{KEY}* 2. If file exists → use title/frontmatter summary 3. If not found → query Atlassian MCP for ticket summary 4. If Jira returns data → use summary, offer to create vault note 5. If Jira unavailable → use key as-is ``` -------------------------------- ### Execute Triage Command Source: https://github.com/borisvu/obsidian-vault-cowork-plugins/blob/master/para-flow/commands/triage.md This snippet demonstrates how to invoke the Triage Command from the command line. It initiates the process of scanning, classifying, and presenting a plan for inbox files. ```shell /para-flow:triage → scan, classify, present plan, ask to proceed ``` -------------------------------- ### Triage Inbox Files with /para-flow:triage Source: https://context7.com/borisvu/obsidian-vault-cowork-plugins/llms.txt Scans the PARA/0 Inbox/ directory, classifies files by content and quality, detects conflicts with existing vault notes, and executes confirmed actions. It provides a detailed breakdown of proposed actions like deletion, moving to the vault, and conflict resolution. ```bash # Triage inbox files /para-flow:triage # Expected output: # ## Delete (empty/temporary) # # | # | File | Reason | # |---|------|--------| # | 1 | SN Agent.md | Empty — only frontmatter, no content | # | 2 | Stuck copy flow investigation.md | Single URL, no context | # # ## Move to vault # # | # | File | Type | Target | Enhancement | # |---|------|------|--------|-------------| # | 3 | Update Set.md | Term | Resources/Terms/ | +tags: servicenow, term | # | 4 | PROJECT-7292 - Audit operation... | Jira | Resources/Jira/ | Already well-structured | # | 5 | Damien Davis.md | Person | Areas/People/ | +tags: person | # # ## Conflicts with existing notes # # | # | Inbox file | Existing note | Signal | # |---|------------|---------------|--------| # | 6 | Damien Davis.md | People/Damien Davis.md | Exact filename match | # # Proceed with this plan? # - Items 1-2: delete # - Items 3-5: move + enhance # - Item 6: conflicts — keep inbox, keep existing, merge, or skip? # Post-triage summary: # Inbox triage complete: # Deleted: 2 files (empty/temporary) # Moved: 3 files (1 person, 1 Jira, 1 term) # Conflicts: 1 resolved (merged) # CLAUDE.md: 1 person added to People table # Inbox: 0 files remaining ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.