improve
/improve
Use to log, prioritize, move, or review COURSE IMPROVEMENTS — the local kanban backlog in the course's `IMPROVEMENTS.md`. Load whenever an audit surfaces findings, the user notes something to fix / try / revisit, a handoff lands action items, or you're asked "what's on the board / what's next / show the backlog / log this". Each improvement is a card that moves Backlog → Ready → In Progress → In Review → Done. This is CONTINUOUS IMPROVEMENT (kaizen) for the course — NOT continuous integration / CI pipelines / GitHub Actions.
- Author
- chaz-clark ↗
- Repository
- canvas-toolbox ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Use to log, prioritize, move, or review COURSE IMPROVEMENTS — the local kanban backlog in the course's `IMPROVEMENTS.md`. Load whenever an audit surfaces findings, the user notes something to fix / try / revisit, a handoff lands action items, or you're asked "what's on the board / what's next / show the backlog / log this". Each improvement is a card that moves Backlog → Ready → In Progress → In Review → Done. This is CONTINUOUS IMPROVEMENT (kaizen) for the course — NOT continuous integration / CI pipelines / GitHub Actions.
Triggers from the description
Original author description
Use to log, prioritize, move, or review COURSE IMPROVEMENTS — the local kanban backlog in the course's `IMPROVEMENTS.md`. Load whenever an audit surfaces findings, the user notes something to fix / try / revisit, a handoff lands action items, or you're asked "what's on the board / what's next / show the backlog / log this". Each improvement is a card that moves Backlog → Ready → In Progress → In Review → Done. This is CONTINUOUS IMPROVEMENT (kaizen) for the course — NOT continuous integration / CI pipelines / GitHub Actions.
How it works
- The board
- The one rule
- Columns (the lifecycle)
- Card schema
- How to work it (lightweight agile — solo-instructor scale)
- Phrases that load this
- Where it plugs in
SKILL.md preview
--- name: improve description: Use to log, prioritize, move, or review COURSE IMPROVEMENTS — the local kanban backlog in the course's `IMPROVEMENTS.md`. Load whenever an audit surfaces findings, the user notes something to fix / try / revisit, a handoff lands action items, or you're asked "what's on the board / what's next / show the backlog / log this". Each improvement is a card that moves Backlog → Ready → In Progress → In Review → Done. This is CONTINUOUS IMPROVEMENT (kaizen) for the course — NOT continuous integration / CI pipelines / GitHub Actions. --- # Improve — the course continuous-improvement board Every course accumulates "should fix / should try" items — from audits, from teaching a term, from the instructor noticing something. Left in chat or one-off letters, they're lost by the next session. This skill keeps them in **one local, git-tracked kanban board** so improvements are tracked to *done*, not rediscovered every term. ## The board **`IMPROVEMENTS.md` at the course root.** Git-tracked (travels with the repo), plain markdown (the instructor can edit it directly), no external service. If it doesn't exist yet, copy `IMPROVEMENTS.template.md` from this skill to create it — confirm with the instructor the first time. ## The one rule **When an improvement is found — by an audit, by the instructor, by a handoff — it becomes a card on the board. When it's worked, it moves through the columns. Nothing that matters gets left only in chat.** ## Columns (the lifecycle) `🗄 Backlog` (unordered ideas) → `🔴 Ready` (prioritized; top = next) → `🟡 In Progress` (being worked) → `🔵 In Review` (done but unverified — awaiting the instructor) → `✅ Done` (verified, linked to the PR/commit that closed it). ## Card schema One line per card, compact: ``` - **[C-###] Short title** — src: <audit YYYY-MM-DD | user | handoff | session> · size <S/M/L> · risk <low/med/high> · <link when it moves> ``` - **id** `C-###` — stable, monotonic; never reused. Assign the next free number. - **src** — where it came from + date, so provenance survives. - **size / risk** — rough, for ordering. No story points. - **link** — the PR/commit/handoff, added as the card moves to In Review / Done. ## How to work it (lightweight agile — solo-instructor scale) - **Log**: new find → a `Backlog` card (or straight to `Ready` if it's clearly next). Audits write their findings here **as cards**, not as a separate lost letter. - **Prioritize**: order `Ready` so the **top is the next thing** to pull. Tag size/risk. - **Pull, don't push**: start work by pulling the top of `Ready` into `In Progress`. **WIP limit: keep `In Progress` small (≈2).** Finish before starting. - **Review gate**: work lands in `In Review`, not `Done`, until the instructor has seen/verified it. Nothing self-marks Done. - **Close**: move to `Done` with the PR/commit link and the date. Keep Done as the record (prune only when it's long). - **Age**: flag a card that's sat in `In Progress`/`In Review` too long — surface it. ## Phrases that load this "log this / add to the board", "what's on the board / show the backlog", "what's next / what should I work on", "move C-012 to in progress / done", "prioritize the board", "turn the audit into cards". ## Where it plugs in - **`audit`** — an audit's output is a set of `IMPROVEMENTS.md` cards (with `src: audit <date>`), so findings are tracked to closure instead of filed and forgotten. - **Handoffs** — a received handoff's action items become cards. - The board is course context (no student PII) — **Zone-1**, safe to read and commit. <!-- GENERATED by lib/tools/generate_adapters.py from skills/improve/SKILL.md — do not edit this copy directly; edit the canonical file and regenerate. schema_version: 1 -->
Files in this package (2)
- IMPROVEMENTS.template.md 1 KB
- SKILL.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · chaz-clark/canvas-toolbox | 100 | MIT |
| terencebristol/terencebristol-toolkit | 100 | MIT |
| spencerbeggs/effected | 100 | MIT |
| crbnos/carbon | 100 | AGPL-3.0 |
| zixwei/AI-Fleet-skills | 100 | MIT |
| notque/vexjoy-agent | 100 | MIT |
| motiondivision/motion | 100 | MIT |
| relai-ai/agent-eval-loop | 100 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 557245b73161 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90Backlog Management
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md. - 100canvas-course-audit
Audit an entire Canvas LMS course against the Four Learning Design Pillars (Clear Structure, Active Content, Continuous Practice, Intuitive UX). Use when users want to evaluate course quality, identify improvement areas, or prepare for course redesign. Requires canvas-mcp server… - 100course-builder
Design course architecture and write module content. Use when user says "build a course", "create a course on", "design a learning path", "course outline", "write a module", or "curriculum design". - 100kanban
Manage SpawnForge taskboard tickets — create, view, move, and sync to GitHub. Use when creating tickets, checking board state, syncing to GitHub before PRs, or managing the project backlog. - 92apply-improvements
This skill should be used when the user asks to apply improvement proposals ('apply improvements', 'ap dung improvement proposals') from .claude/improvement-proposals.md (written by pipeline-retrospective) to the plugin files. - 95kaizen
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.