Install
$ agentstack add skill-choral-io-choral-skills-kanban-maintenance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Kanban Maintenance
Runtime Context
Before acting, resolve ` using the runtime bootstrap rules, then read /.workflow/runtime.md and /.workflow/manifest.yml`; do not assume non-default workflow paths or default ids.
Use this skill to apply approved changes to /planning/KANBAN.md.
Preconditions
- A maintainer has explicitly approved the Kanban change.
- The proposed card links to project knowledge or a task item.
- The card is not a duplicate of an active card.
Workflow
- Read
/.workflow/rules/delivery.md. - Open
/planning/KANBAN.md. - Resolve card wikilinks to task items by task id or file basename.
- Check the requested transition against the Move Matrix in
references/cards.md. - Apply only the approved board changes.
- Keep cards thin and linked.
- Preserve the column order.
- For
Reviewing -> Done, report whether dependency follow-up was approved, deferred, or not applicable. - For new accepted tasks with planned dependencies, place cards in
Backlogunless the approved dry run explicitly selectsReady. - Report exact cards moved, added, changed, or removed.
Guardrails
- Do not edit unrelated cards.
- Do not use localized files as card sources.
- Do not duplicate acceptance criteria or long discussion in the board.
- Stop and report ambiguity if a card link can match multiple canonical files.
- When moving a card to
Blocked, keep the board card thin and ensure blocker details live in the linked task item. - Do not move a new dependent task to
Blockedonly because it hasblocked_by; useBacklogplus task readiness metadata until the work was expected to proceed. - Move out of
Blockedonly to the approved next state:Readywhen no one is actively handling it,Doingwhen the current handler is continuing it, orBacklogwhen it still needs refinement. - Do not move
Reviewing -> Donewhile known dependency follow-up is unresolved unless the maintainer explicitly defers it. - Stop if the requested change conflicts with the Kanban workflow.
References
- For card and column examples, read
references/cards.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: choral-io
- Source: choral-io/choral-skills
- License: MIT
- Homepage: https://github.com/choral-io/choral-skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.