| name | kanon-agent |
| description | Project board PM assistant — create issues, manage cycles, capture roadmap items, SDD hooks. |
| trigger | list issues, create issue, update issue, close issue, board management, start cycle, close sprint, roadmap item, track this, log a bug, deferred work |
Core Philosophy
One issue = one unit of work. Every card must be readable by a teammate who never touched the code.
Human-readable titles, not internal paths.
Issue Lifecycle
- kanon_list_groups(projectKey) → pick groupKey
- kanon_create_issue with [Area] title + group + description
- kanon_start_work(issueKey)
- kanon_transition_issue: backlog → todo → in_progress → review → done
- kanon_update_issue: enrich description as work evolves
- Deferred/later work → kanon_create_roadmap_item, NOT backlog
- kanon_stop_work when done
Title Format
Pattern: [Area] Imperative verb phrase
- Good:
[Auth] Fix OAuth redirect | [API] Add rate limiting
- Bad:
fix thing | sdd/change/path | KAN-42
Always call kanon_list_groups before creating an issue — assign a real groupKey.
Design Records
Use kanon_create_document (kind: adr|pdr|rfc|note). Propose before creating — human approves.
PROPOSE when: real alternatives existed AND lasting consequences (architecture, API contracts, conventions).
Skip: routine fixes, refactors, work logs, cosmetic changes, obvious-only-choice situations.
Template: ## Context / ## Decision / ## Alternatives Considered / ## Consequences
Good: "Chose Redis for sessions — native TTL, evaluated Memcached" → propose ✓ Bad: "Fixed typo" → skip ✗
On-Demand Sections
| Trigger | Section |
|---|
| Issue create flow, field mapping, existence checks | issue-creation.md |
| Roadmap, deferred capture, promote-to-issue | roadmap.md |
| Cycle lifecycle, scope, close dispositions | cycle.md |
| SDD hooks, deferred_items, ROADMAP injection | sdd-hooks.md |
