@orderful/droid 0.6.0 → 0.7.0

package/src/skills/brain-obsidian/references/templates.md

@@ -0,0 +1,144 @@
+# Obsidian Brain Templates
+
+Templates with YAML frontmatter and wikilink support.
+
+## Plan Template
+
+```markdown
+---
+type: plan
+status: exploring
+created: {date}
+updated: {date}
+project: "[[{project}]]"
+tags: []
+---
+
+# {Topic}
+
+Planning {brief description}.
+
+## Context
+
+What we're solving and why.
+
+## Exploration
+
+Options and approaches considered.
+
+## Decision
+
+What we chose and why.
+
+## Next Steps
+
+- [ ] Action items
+```
+
+## Research Template
+
+```markdown
+---
+type: research
+status: exploring
+created: {date}
+updated: {date}
+project: "[[{project}]]"
+tags: []
+---
+
+# {Topic}
+
+Researching {brief description}.
+
+## Questions
+
+What we're trying to understand.
+
+## Findings
+
+What we've learned.
+
+## Summary
+
+Key takeaways.
+
+## Related
+
+- [[related-note-1]]
+- [[related-note-2]]
+```
+
+## Review Template
+
+```markdown
+---
+type: review
+status: exploring
+created: {date}
+updated: {date}
+project: "[[{project}]]"
+tags: []
+---
+
+# {Topic}
+
+Reviewing {brief description}.
+
+## Overview
+
+What's being reviewed and scope.
+
+## Observations
+
+Key findings and notes.
+
+## Recommendations
+
+Suggested changes or actions.
+
+## Verdict
+
+Overall assessment.
+```
+
+## Note Template
+
+```markdown
+---
+type: note
+created: {date}
+tags: []
+---
+
+# {Brief Title}
+
+{content}
+```
+
+## Template Variables
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{Topic}` | Doc title from user input | "Auth Refactor" |
+| `{date}` | Current date (YYYY-MM-DD) | "2025-01-15" |
+| `{brief description}` | Context from conversation | "refactoring the authentication system" |
+| `{project}` | Active project name (if any) | "transaction-templates" |
+| `{content}` | User-provided text | (for notes) |
+
+## Frontmatter Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `type` | string | Doc type: `plan`, `research`, `review`, `note` |
+| `status` | string | Lifecycle: `exploring`, `drafting`, `decided`, `done`, `stale` |
+| `created` | date | Creation date (YYYY-MM-DD) |
+| `updated` | date | Last modification date |
+| `project` | wikilink | Link to related project: `"[[project-name]]"` |
+| `tags` | list | Tags for filtering: `[tag1, tag2]` |
+
+## Wikilink Conventions
+
+- Project links: `[[project-name]]` or `[[1-Projects/project-name/PROJECT]]`
+- Related notes: `[[note-name]]`
+- Use Obsidian's autocomplete to find existing notes

package/src/skills/brain-obsidian/references/workflows.md

@@ -0,0 +1,192 @@
+# Obsidian Brain Workflows
+
+Obsidian-specific procedures that override brain defaults.
+
+## Creating Docs
+
+**Overrides:** brain's Creating workflow
+
+**Steps:**
+
+1. **Resolve paths from config:**
+   - `brain_dir` from brain skill (your vault path)
+   - `inbox_folder` from brain-obsidian (default: `0-Inbox`)
+
+2. **Target folder:** `{brain_dir}/{inbox_folder}/`
+
+3. **Generate filename** using brain's naming conventions:
+   - Format: `{type}-{topic-slug}.md`
+
+4. **Check for active project:**
+   - If `/project` was loaded this session, use its name for `project` field
+   - Otherwise, leave `project` field empty or ask user
+
+5. **Apply Obsidian template** from `references/templates.md`:
+   - Include YAML frontmatter with all fields
+   - Set `created` and `updated` to today
+   - Set `status: exploring`
+
+6. **Create the file** in vault
+
+7. **Set as active doc** (same as brain)
+
+## Opening Docs
+
+**Overrides:** brain's Opening workflow
+
+**Steps:**
+
+1. **Search in brain_dir** (your vault):
+   ```
+   Glob: {brain_dir}/**/*{topic}*.md
+   ```
+
+2. **Rest of workflow same as brain** (fuzzy match, select, read, set active)
+
+## Updating Frontmatter
+
+When modifying any brain doc:
+
+1. **Update the `updated` field** to current date
+2. **Update `status`** if work has progressed
+3. **Add `project` link** if doc becomes associated with a project
+
+## Finalizing
+
+**Overrides:** brain's Finalizing workflow
+
+**Steps:**
+
+1. **Read active doc** and current location
+
+2. **Update frontmatter:**
+   - Set `status: done`
+   - Update `updated` date
+
+3. **Suggest destination based on content and config:**
+
+   **Without PARA (`para_structure: false`):**
+   | Condition | Suggested Destination |
+   |-----------|----------------------|
+   | Done/stale | `{archive_folder}/` |
+   | Still useful in inbox | Keep in place |
+
+   **With PARA (`para_structure: true`):**
+   | Condition | Suggested Destination |
+   |-----------|----------------------|
+   | Has active project link | `{projects_folder}/` |
+   | Ongoing area of responsibility | `{areas_folder}/` |
+   | Reference/learning value | `{resources_folder}/` |
+   | Stale or obsolete | `{archive_folder}/` |
+
+4. **Confirm move with user** before relocating
+
+5. **Move the file** if confirmed:
+   ```bash
+   mv "{brain_dir}/{inbox_folder}/{file}" "{brain_dir}/{destination}/{file}"
+   ```
+
+6. **Clear active doc** from session
+
+## Quick Notes
+
+**Overrides:** brain's Notes workflow
+
+**Steps:**
+
+1. **Create in inbox:** `{brain_dir}/{inbox_folder}/note-{date}-{slug}.md`
+
+2. **Use note template** with minimal frontmatter:
+   ```yaml
+   ---
+   type: note
+   created: {date}
+   tags: []
+   ---
+   ```
+
+3. **Fire-and-forget** (does not become active)
+
+## Project Integration (Optional)
+
+**Requires:** `project` skill. If not installed, suggest:
+> "Linking to projects requires the project skill. Install it with `droid` → Skills → project"
+
+When a project is loaded via `/project {name}`:
+
+1. **Remember project name** for session
+2. **New brain docs** automatically get `project: "[[{name}]]"` in frontmatter
+3. **Suggest linking** existing brain docs to the project
+
+## Adding Brain Doc to Existing Project
+
+**Trigger:** User says "add this to the project", "link this to project", or "capture in project"
+
+**Requires:** `project` skill. If not installed, suggest:
+> "Linking to projects requires the project skill. Install it with `droid` → Skills → project"
+
+For linking a brain doc (research, notes, design) to an existing project.
+
+**Steps:**
+
+1. **Check for active project:**
+   - If project loaded via `/project`, use that
+   - Otherwise, ask which project to link to
+
+2. **Update brain doc frontmatter:**
+   - Add `project: "[[{project-name}]]"`
+   - Update status if appropriate
+
+3. **Update project:**
+   - Add wikilink in Related section: `[[{brain-doc}]]`
+   - Or add to appropriate section (Key Decisions, Implementation, etc.)
+
+4. **Suggest moving brain doc:**
+   - With PARA: move to `{projects_folder}/` alongside project
+   - Without PARA: keep in place with project link
+
+## Promoting Brain Doc to New Project
+
+**Trigger:** User says "promote to project", "make this a project", or "convert to project"
+
+**Requires:** `project` skill. If not installed, suggest:
+> "Promoting to project requires the project skill. Install it with `droid` → Skills → project"
+
+For graduating a full tech design or plan into its own project.
+
+**Steps:**
+
+1. **Confirm promotion:**
+   - "This will create a new project from this brain doc. Continue?"
+
+2. **Extract project info from brain doc:**
+   - Title → project name
+   - Context → project overview
+   - Decision/Next Steps → initial tasks
+   - Status → project status
+
+3. **Create new project** via project skill:
+   - Generate PROJECT.md from brain doc content
+   - Create CHANGELOG.md with initial entry
+   - Place in projects directory
+
+4. **Update original brain doc:**
+   - Add `project: "[[{new-project}]]"` to frontmatter
+   - Update status to `done`
+   - Add note: "Promoted to project: [[{new-project}]]"
+
+5. **Handle the brain doc:**
+   - Option A: Keep as historical reference in `{resources_folder}/`
+   - Option B: Archive to `{archive_folder}/`
+   - Option C: Delete (content now lives in project)
+
+## Listing Docs
+
+**Overrides:** brain's Listing workflow
+
+Search in vault:
+```
+Glob: {brain_dir}/**/*.md
+```
+
+Filter to brain doc types by checking frontmatter for `type: plan|research|review|note`.