From canon
Load spec context for the current task. Use when starting work on a feature, investigating a bug, or reviewing code that relates to a spec. Automatically identifies relevant specs from git changes or a user-provided topic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/canon:canon-contextThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are loading spec context for the user's current task.
You are loading spec context for the user's current task.
Check what the user is currently working on:
git diff --name-only HEAD 2>/dev/null || git diff --name-only --cached 2>/dev/null || echo ""
If the user provided a topic, use that instead of git changes.
With MCP (preferred): Use mcp__canon__search to find specs matching changed files or the topic.
Without MCP (fallback): Search locally:
Glob to find all specs: docs/specs/*.mdGrep to search spec content for terms from changed files or topicRead to load matching spec filesFor each relevant spec, present:
Specs use YAML frontmatter:
---
title: "Feature Name"
type: spec # spec, proposal, design, adr
status: draft # draft, in_progress, done, deprecated
owner: "name"
team: "team-name"
tags: [tag1, tag2]
---
Sections are numbered headings (## 1. Section Title).
Status comments: <!-- canon:system:1.1 status:todo -->
Ticket links: <!-- canon:ticket:github:ORG-123 -->
AC checkboxes: - [ ] Unchecked / - [x] Checked
npx claudepluginhub canonhq/canon --plugin canonWrite and manage spec files with search, conflict detection, and reporting. Use when user asks to create a spec, update a spec, write a spec, or mentions 스펙 생성, 스펙 업데이트, 스펙 작성, 스펙 만들어줘. Proactively trigger whenever the user's request involves specification documents, even if they don't explicitly say "spec".
Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.
Manages specification files with template-driven creation, duplicate detection, and conflict reporting. Automatically activates when creating or updating specs.