canon

Manage software development workflows with Obsidian vault notes for tasks and handoffs.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/eannnnnn/taptik-labs --skill canon-eannnnnn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canon
Source: https://github.com/eannnnnn/taptik-labs/tree/main/skills/canon
Command: npx skills add https://github.com/eannnnnn/taptik-labs --skill canon-eannnnnn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines complex software development tasks by using Obsidian as the central source of truth for feature specifications, task management, and historical tracking, preventing data loss and improving collaboration.

Core Features & Use Cases

  • Centralized Knowledge: Manages feature details, plans, and task status within Obsidian vault notes.
  • Workflow Enforcement: Guides users through a structured process for creating, updating, and handing off complex work items.
  • Use Case: A developer needs to implement a new authentication module. They use this Skill to create a feature note in Obsidian, detailing the plan, acceptance criteria, and tasks. As they work, they update the note, and if they need to hand off the task, they use the Skill to record the handover explicitly.

Quick Start

Use the canon skill to create a new feature note for the 'user-profile' project under the 'authentication' domain.

Frequently Asked Questions about canon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage complex software development tasks in Obsidian?

You manage complex software development tasks in Obsidian by using a structured workflow Skill to centralize feature specifications, track task states, and record session handoffs directly within Markdown notes.

How does Obsidian-based task management handle session handoffs?

Obsidian-based task management handles session handoffs by explicitly recording the handover within the feature note, ensuring data integrity through atomic updates and explicit ownership tracking.

Can I use Obsidian as the primary data store for feature specifications and workflow states?

Yes, you can use Obsidian as the primary data store for feature specifications and workflow states. The Skill enforces an Obsidian-first approach, preventing local file manipulation outside the vault.

What is the best way to prevent data loss when tracking complex feature plans in Markdown notes?

The best way to prevent data loss when tracking feature plans in Markdown notes is to enforce a centralized source of truth with atomic updates and explicit ownership tracking during task handoffs.

Does this task management approach require external databases outside of Obsidian?

No, this approach does not require external databases outside of Obsidian. It uses an Obsidian-first architecture to manage historical logging and structured task states entirely within your vault.