canvas-update

Identify canvas sections needing updates and log evidence-backed changes in decision-log.md.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill canvas-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canvas-update
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/canvas-update
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill canvas-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canvas updates often occur without explicit sources and can drift out of sync across related files. This skill enforces evidence-backed changes and maintains cross-file consistency.

Core Features & Use Cases

  • Enforce evidence at every update to the canvas.
  • Maintain cross-file consistency when related canvases or files change.
  • Log updates in decision-log.md to preserve rationale and traceability.

Quick Start

Provide a new evidence source for the latest canvas update and commit the change with a summary in the decision-log.

Frequently Asked Questions about canvas-update

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

FAQPage Schema
How do I keep canvas updates evidence-based and consistent across multiple files?

To keep canvas updates evidence-based, you must provide an explicit source for every change and apply it across all canvases listed in the matrix. This prevents files from drifting out of sync and maintains cross-file consistency.

How do I log product management decisions to preserve rationale and traceability?

You log product management decisions by recording updates with evidence and notes in decision-log.md. This preserves the rationale and traceability of canvas changes for future governance and auditing.

What is the best way to manage canvas governance and prevent workflow drift?

Canvas governance is best managed by enforcing evidence-backed changes at every update and logging them in decision-log.md. This approach prevents untracked modifications and stops related files from drifting out of sync.

Can I update related canvases without breaking consistency with existing logs?

Yes, you can update related canvases without breaking consistency by applying changes across all files listed in the matrix and logging the update with evidence in decision-log.md to preserve traceability.

Why do canvas updates require explicit sources before committing changes?

Canvas updates require explicit sources to enforce evidence-based governance and prevent undocumented drift. Committing changes with a summary in the decision-log ensures rationale is preserved and traceable.