Decisions

  • Pending: What Trello functionality to replicate first?
  • Pending: Obsidian-native or separate tool?
  • Pending: How to handle recurring tasks?

User Tasks


Summary

Replace Trello with a personal task management system inside the Opus vault — boards, lists, and cards managed through markdown.

Problem / Motivation

  • Trello is an external dependency for personal task management.
  • Tasks live outside the vault — no integration with FRs, knowledge, or daily workflows.
  • Context-switching between Trello and Obsidian/Claude slows things down.
  • Having everything in one system enables automation (e.g., auto-prioritize, daily briefing integration).

Proposed Solution

A markdown-based task management system in the vault that covers the core Trello workflow: boards with columns, cards with descriptions/labels/due dates, and a way to move tasks through stages.


Open Questions

1. Scope — What Trello features matter most?

Question: Which Trello features do you actually use day-to-day?

OptionDescription
A) Kanban boards + cardsColumns (e.g., To Do / Doing / Done), cards with titles and descriptions
B) + Labels & due datesA plus filtering/sorting by label, priority, and deadline
C) + Checklists & attachmentsFull card detail with sub-tasks and linked files
D) All of the aboveComplete Trello replacement

Recommendation: Start with A, expand based on actual need.

Decision:

2. Structure

Question: How should tasks be organized in the vault?

OptionDescription
A) Single file per boardOne markdown file per board with tasks as list items
B) File per taskEach task is its own file (like FRs), boards are folders
C) Obsidian Kanban pluginUse the community plugin for native drag-and-drop

Recommendation: Option A — lightweight, easy to scan, works with Claude skills.

Decision:

3. Board Categories

Question: What boards do you currently have in Trello?

Need user input — list your current Trello boards so we can map them to the new system.

Decision:

4. Integration

Question: Should tasks connect to the rest of Opus?

OptionDescription
A) Standalone firstTask system works independently, integrate later
B) Integrated from startLink tasks to FRs, include in daily briefings, etc.

Recommendation: Option A — get the basics right first, then wire it up.

Decision:


Phase Overview

PhaseDescriptionStatus
Phase 1Basic Kanban boards in markdown + management skill
Phase 2Labels, priorities, due dates, filtering
Phase 3Integration with daily briefings, FRs, and automation

Phase 1: Basic Kanban Boards —

Goal: Replace core Trello workflow — boards with columns and movable tasks.

File / FeatureDetailsOwnerStatus
vault/my-todos.md or vault/tasks/Task board location (TBD)opus
.claude/skills/task/SKILL.mdSkill to add/move/list tasksopus
Board templateReusable board formatopus

Phase 2: Enrichment —

Goal: Add metadata to tasks — labels, priorities, due dates, filtering.

File / FeatureDetailsOwnerStatus
Task metadata formatPriority, labels, due date syntaxopus
Filter/sort skillView tasks by priority, due date, labelopus

Phase 3: Integration —

Goal: Wire task system into Opus workflows.

File / FeatureDetailsOwnerStatus
Daily briefing integrationShow today’s tasks in briefingopus
FR linkingLink tasks to feature requestsopus
Recurring tasksAuto-generate repeating tasksopus

Test

Manual tests

TestExpectedActualLast
pending-

AI-verified tests

ScenarioExpected behaviorVerification method

E2E tests

ScenarioAssertion

Integration tests

ComponentCoverage

Unit tests

ComponentTestsCoverage

History

DateEventDetails
2026-03-04CreatedInitial FR — Trello replacement

References

  • FR-038 — Kanban Feature Overview (similar Kanban pattern, could share rendering logic)
  • vault/my-todos.md — existing quick todo file