kanban-card-run
Skill6 starsChanged 3 months agoMITView on GitHub
Operate the project Kanban board: create, groom, start, move, review and complete cards through the board helpers, with owner decisions and lifecycle rules. Use when managing tasks or cards. RU: канбан, задачи, карточки, взять задачу, закрыть задачу.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/agent-hook-verify/references/claude.mdCLAUDE.md
- agent-command-runSkill
- agent-context-auditSkill
- agent-hook-verifySkill
- agent-integration-auditSkill
- agent-model-findSkill
- agent-project-syncSkill
- agent-skill-findSkill
- agent-skill-syncSkill
- agent-terms-defineSkill
- agent-workspace-migrateSkill
- api-contract-defineSkill
- api-docs-syncSkill
- api-stream-diagnoseSkill
- api-yandex-oauth-runSkill
- code-async-reviewSkill
- code-cli-buildSkill
- code-config-auditSkill
- code-durable-reviewSkill
- code-performance-fixSkill
- code-state-verifySkill
- deploy-artifact-publishSkill
- deploy-rollout-runSkill
- design-brand-buildSkill
- docs-claims-verifySkill
- docs-diagram-buildSkill
- docs-prose-fixSkill
- git-branch-cleanSkill
- git-merge-syncSkill
- git-path-runSkill
- git-repo-runSkill
- git-worktree-guardSkill
- infra-container-setupSkill
- infra-network-diagnoseSkill
- infra-project-migrateSkill
- infra-runbook-buildSkill
- kanban-board-auditSkill
- kanban-card-buildSkill
- kanban-card-planSkill
- kanban-card-reviewSkill
- kanban-card-verifySkill
- kanban-epic-coordinateSkill
- kanban-queue-coordinateSkill
- kanban-roadmap-planSkill
- kanban-schedule-runSkill
- monitor-telemetry-setupSkill
- personal-action-planSkill
- quality-artifact-verifySkill
- quality-change-reviewSkill
- quality-change-verifySkill
- research-prior-art-findSkill
- research-source-auditSkill
- research-source-findSkill
- research-spike-runSkill
- security-access-diagnoseSkill
- security-api-hardenSkill
- security-boundary-hardenSkill
- security-boundary-reviewSkill
- security-filesystem-hardenSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. About 0 are common, 18 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use for starting, moving, grooming, reviewing or completing tasks on a project Kanban board.
- Very specific: line 47
When the current user or applicable project workflow requires explicit user approval for done, preserve that requirement.
- Distinctive: line 64
Check each action independently.
- Very specific: line 76
Every card carries <PREFIX>-<NUM> or a legacy letter-suffixed ID <PREFIX>-<NUM><LETTER> (epic subtasks: <PREFIX>-<NUM>-<NN>, see Epics …
- Distinctive: line 138
Read the card's open questions and identify decisions needed for a safe, implementable task.
- Distinctive: line 141
Ask the user only when a material choice or authorization is genuinely missing, using an available runtime question interface, and continue …
- Very specific: line 151
Brief the user first (interactive starts): Before moving the card to progress/, post a short, plain-language task briefing to the user in …
- Very specific: line 159
From description: create from task template in todo/, then move to progress/ (only if scope is clear).
- Distinctive: line 163
Read the task file. Plan and track appropriately scoped subtasks using the runtime interface available for this task.
- Distinctive: line 164
Add "Execution Log" section to the task file.
- Distinctive: line 173
Use the canonical move helper, then refresh the latest ready-card body and any remaining owned task files.
- Distinctive: line 192
Verify the task branch is clean (git status --short empty — everything committed, nothing stray left uncommitted).
- Distinctive: line 194
Only then squash-merge the branch into the default branch if merge is also authorized for this target (see Git Commits below).
- Very specific: line 197
If done authorization is missing, retain ready/ and identify the missing grant.
- Very specific: line 250
Integration: When the last subtask reaches ready/: restart the project, refresh all data (re-run imports/migrations), and run the full test …
- Very specific: line 252
Hand-off: Only then move the epic card to ready/.
- Distinctive: line 269
Sub-agent commits: When local commits are authorized, each sub-agent commits only its own work, following the repository's message and …
- Distinctive: line 272
Normal local commits: Commit coherent, validated progress proactively when useful.
- Distinctive: line 276
Do not create an empty or redundant commit when that exact owned state is already committed and verified.
- Distinctive: line 296
Do NOT skip planning.
- Very specific: line 297
Do NOT perform done, merge, push, or deploy without valid authorization explicitly covering that action and target.
- Very specific: line 300
Do NOT start a card from grooming/ — resolve open questions, move to todo/ first.
- Very specific: line 303
Do NOT move to ready/ while tests are red.
- Distinctive: line 304
Do NOT fix out-of-scope findings solely because they are small.
- Very specific: line 315
test-engineerwrites tests, not business logic: If a test needs a new endpoint/hook in the code → file a subtask in kanban and delegate … - Distinctive: line 318
New agent — only when clearly needed: If the task fits an existing agent — don't spawn extra agents.
- Distinctive: line 323
Use for starting, moving, reviewing, or completing tasks on a project Kanban board.
- Very specific: line 332
Follow the project's defined transitions.
- Distinctive: line 334
If the owner explicitly classifies a card as superseded, history-only, or merged into another card, record the decision and receiving card, …
- Distinctive: line 335
Add concise execution-log entries after material work, verification, operational actions, or blockers, using the language required by the …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kanban cards
Use for starting, moving, grooming, reviewing or completing tasks on a project Kanban board. The first section is the full manual and script reference; the second adds the day-to-day operating rules.
Kanban manual
Stages
| Stage | Canonical path | Description |
| Grooming | .agents/kanban/grooming/ | Draft tasks with open questions / unresolved scope |
| Todo | .agents/kanban/todo/ | Refined tasks ready to start |
| Progress | .agents/kanban/progress/ | Currently being worked on |
| Test | .agents/kanban/test/ | Implementation handed off; review/QA in progress |
| Ready | .agents/kanban/ready/ | Evidence checkpoint; awaiting authorized finalization |
| Done | .agents/kanban/done/ | Authorized successful completion |
| Freeze | .agents/kanban/freeze/ | Temporarily paused work awaiting its recorded return condition |
| Closed | .agents/kanban/closed/ | Cancelled or superseded work; terminal archive |
Lifecycle: grooming → todo → progress → test → ready → done.
New boards default to .agents/kanban. Resolve an existing board and its
kanban.lock through the project helper. Aliases to the same physical path are
one board; distinct conflicting boards or counters fail closed. For an existing
legacy board, consult board compatibility.
freeze/ is a side state: enter from grooming/, todo/, progress/, test/,
or ready/; resume the same card only to todo/ or progress/ with
--resume. Record the pause reason and return condition in **Decisions:**.
closed/ records cancellation/supersession, not successful completion; entering
it from any nonterminal stage, including freeze/, requires --approved.
closed/ is terminal even with --force; future work gets a new linked card.
Both stages participate in board-wide ID uniqueness checks.
Autonomous runs never enter grooming/. ready/ is a mandatory evidence and
verified local-commit checkpoint, not a compulsory human stop. Continue with
authorized actions when their action-specific authorization and gates pass.
The narrow kanban-schedule-run merge-at-ready exception preserves its exact approved
card allowlist and QA/review gates; the manifest alone does not authorize done,
push or deploy.
When the current user or applicable project workflow requires explicit user
approval for done, preserve that requirement. Standing profile or agent
authority is not a substitute for the required user approval.
Authorization for automated lifecycle actions
done, merge, push, and deploy may and should proceed automatically when the
executing profile/agent already holds valid authorization for that specific
action, target project/task, and applicable limits, and all mandatory
acceptance, quality, review, and operational gates pass. Do not request another
user confirmation merely because execution is automated or a card reached
ready. Valid sources include explicit user approval at hand-off, recorded
EPIC-scoped upfront autonomous authorization for its named scope, other
recorded upfront task/workflow authorization, or recorded profile/agent authorization
(standing owner-approved authority assigned to that profile/agent). Existing
valid grants remain effective within their scope.
Check each action independently. Record the authorization source/reference,
executing profile/agent, covered actions and limits, target, and result in the
card. A profile name, credentials, green tests, or stage transition alone is
not a grant. This policy itself grants no production or release permission;
explicit task restrictions and native security/approval controls remain
binding, and a refusal must not be bypassed. ready does not imply done,
merge, push, or deploy authorization. done alone does not authorize merge,
push, or deploy; no grant extends to later EPICs or scope expansion unless it
explicitly includes them.
IDs & Prefix
Every card carries <PREFIX>-<NUM> or a legacy letter-suffixed ID
<PREFIX>-<NUM><LETTER> (epic subtasks: <PREFIX>-<NUM>-<NN>, see Epics
below). Counters live in the committed kanban.lock beside the resolved board
root; allocation uses a companion flock marker and reconciles against cards
actually on the board on every allocation — a stale counter after a merge
can't hand out a duplicate ID. The ID parser preserves the optional letter, so
K-094a and K-094b are distinct IDs; slug words such as css-grid are not
prefix candidates.
First use in a project (no prefix= yet) is a confirmation, never a
guess. kanban-id.sh next/prefix exits 2 with the board's candidate
prefixes (existing board cards win by count if any, else a dir-name-derived
one) — on that exit, ask the user which to use via the runtime's available
question interface (present candidates and a recommendation), then run
kanban-id.sh set-prefix <PREFIX> to confirm it; don't auto-pick and don't
retry silently. Full mechanics, lock format, prefix registry →
scripts.md.
The adjacent .flock file coordinates only processes that open the same
resolved lock file. Separate Git worktrees have separate tracked counters and
lock markers; until a shared allocator exists, one canonical board owner must
allocate IDs and perform lifecycle moves from the canonical checkout. Task
worktrees do not allocate IDs or mutate board stages.
Scripts
Set ROOT="${AI_AGENTS_SKILLS_ROOT:-${CLAUDE_PLUGIN_ROOT:-${PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-}}}}" and
S="$ROOT/skills/kanban-card-run/scripts", then invoke every script below as "$S"/<name> — never by bare name
(optional leading --repo <path>, default git toplevel):
| Script | Purpose | Key flag |
"$S"/kanban-id.sh | allocate/inspect IDs (next|epic|sub|peek|prefix) | sub <EPIC-ID> |
"$S"/kanban-new.sh | allocate ID + render template + stage card | --epic|--sub <EPIC-ID> |
"$S"/kanban-move.sh | validated stage transition (uses the bundled Git-aware path helper) | --approved for →done/→closed; --resume from freeze/ |
"$S"/kanban-status.sh | board overview, subtasks grouped under their epic | --epic ID |
"$S"/kanban-lint.sh | card validation (shape, template, dupes, counter drift) | — |
Full CLI, flags, exit codes, worked examples → scripts.md. Manual
fallback requires the resolved board's adjacent kanban.lock; if the Git-aware path skill is needed separately, ask the user to invoke it manually. Never bypass a native refusal.
Task Lifecycle
1. Create
- Default:
"$S"/kanban-new.sh --title "…" --stage todo(or--stage groomingwhen scope isn't settled) — allocates the ID, renders task template, stages the card, prints its path. - Manual fallback: allocate the next ID by hand against the lock beside the resolved board root, fill in task template,
git add. - Scope clear (AC, files, approach all settled) →
todo/. - Open questions remain →
grooming/; list them in**Open questions:**.
Side-found or user-suggested findings
Distinguish a finding from authorization to change it. Fix it only when it is within the active task or otherwise authorized; small size or suitability for a subagent is not permission to expand scope. Before creating a new card, search for a related card to avoid duplicates. Create or update a card or a project scratch list only when that write is in scope and follows the board policy; otherwise report the finding, location and evidence without mutating the board. Preserve existing entries and project conventions. Summarize in-scope repairs and unresolved findings in the handoff.
1a. Groom (grooming/ → todo/)
Read the card's open questions and identify decisions needed for a safe,
implementable task. Resolve routine choices from the existing request and
project policy when those provide sufficient authority; record the rationale.
Ask the user only when a material choice or authorization is genuinely missing,
using an available runtime question interface, and continue independent work
where possible. Do not invent missing approval or silently decide a required
user preference. Record decisions and keep genuinely unresolved questions on
the card; move to todo/ only when the applicable readiness criteria are met.
See reference.md for the grooming protocol.
2. Start (todo → progress)
- Brief the user first (interactive starts). Before moving the card to
progress/, post a short, plain-language task briefing to the user in the user's language: what the task does and why, the acceptance criteria, the planned approach, and which files/areas it touches. It's a read-back so the user can catch a wrong card or misread scope before work starts — keep it concise and explained, don't dump the raw card. Skip only on autonomous/ unattended runs (no user present, e.g. kanban-schedule-run). - From file: move
.agents/kanban/todo/<task>.md→progress/. - From description: create from task template in
todo/, then move toprogress/(only if scope is clear).
3. Implement (progress/)
- Read the task file. Plan and track appropriately scoped subtasks using the runtime interface available for this task.
- Add "Execution Log" section to the task file; update after each significant step.
4. Test (progress → test)
Move card to test/. Run the QA checks required by the project's applicable instructions and test configuration.
5. Ready (test → ready)
Auto-review passed + AC met + tests green → move to ready/. If review finds issues → stay in test/.
Use the canonical move helper, then refresh the latest ready-card body and any
remaining owned task files. Make the normal local wrap-up commit without a
separate permission request, using the configured named Git executor when
routing requires it. Verify the commit SHA, message, committed paths and
reviewed bytes, and confirm no task-owned changes remain uncommitted before
reporting the handoff complete. Do not require a globally empty worktree or
capture unrelated work. If Git, access, or a hook genuinely blocks the commit,
report card ready; commit blocked with evidence. Ready does not authorize
done, merge, push, or deployment.
6. Done (ready → done) — authorized finalization
Authorization for done must be explicit current user approval, recorded
upfront task/EPIC/workflow authorization, or recorded profile/agent
authorization, and must cover this card. Record its source and scope. A grant
for done alone never implies merge, push, deploy, later-EPIC work, scope
expansion, or bypassing tests/review. Order matters — card first, merge last:
- Move the card
ready/ → done/(kanban-move.sh <ID> done --approved). - Verify the task branch is clean (
git status --shortempty — everything committed, nothing stray left uncommitted). - Only then squash-merge the branch into the default branch if merge is also authorized for this target (see Git Commits below).
If done authorization is missing, retain ready/ and identify the missing
grant. In the normal finalization path, merge only after done and clean-branch
verification. If merge authorization is missing, retain the task branch and its
ready/done card and report that the canonical base still has the pre-merge state.
Archive-rename only after a successful, verified, authorized merge. Push and deploy
remain independently authorized actions; read back the exact target and verify
the expected remote revision or deployed version/state before reporting success.
Narrow kanban-schedule-run exception: a task may be squash-merged from ready/
while its card remains in ready/ only when a valid hash-verified scope manifest
lists that exact card, the scope was approved before scheduling, and QA plus an
independent review passed. This exception permits merge-at-ready and chaining only
inside the manifest. The manifest by itself never grants done, push/deploy,
or overrides project-local rules. Those actions may proceed automatically only
under an independently valid action-specific grant and their required gates;
otherwise they remain pending. Do not require a done move to exercise this
explicit merge-at-ready exception.
Freeze and closed
- A card may enter
freeze/fromgrooming/,todo/,progress/,test/, orready/. Add its pause reason and return condition to**Decisions:**; lint does not require new headings for these notes. - Resume from
freeze/totodo/orprogress/only withkanban-move.sh <ID> <stage> --resume.--forcecannot bypass this rule. - Move a cancelled or superseded card to
closed/only withkanban-move.sh <ID> closed --approved. This flag is a caller attestation; the caller must already have explicit user authorization to cancel the work. A card inclosed/cannot be moved out, even with--force; create a new linked card for future work. A successfully completeddone/card cannot be reclassified as cancelled. done/,freeze/, andclosed/skip active-card content-completeness lint, but all exact card IDs across all stages must be unique.
Epics
An epic is a card whose body lists ordered subtask cards. Subtasks are normal cards; the epic is their parent and their integration point.
- Naming — reserved shared ID. The epic always gets an
EPIC-<NUM>ID (kanban-new.sh --epic), independently of the project's regular task prefix; every subtask reuses that SAME ID plus a 2-digit suffix in execution order (kanban-new.sh --sub <EPIC-ID>): e.g.EPIC-042-billing-epic.md,EPIC-042-01-db-schema.md,EPIC-042-02-api-crud.md… Regular cards retain their<PREFIX>-<NUM>IDs. Epic and subtasks share the leading^[A-Za-z][A-Za-z0-9]*-[0-9]+ID token —kanban-schedule-rungroups them as one chain (related-card-first selection, dependency blocking) and the byobu window name stays inside its 10-char cap. - Start. Epic card →
progress/. Create ONE branchepic/<ID>for the whole epic; every subtask is implemented in that branch, not in its owntask/<ID>. - Subtasks. Work them in the listed order. Each finished subtask card moves
progress/ → test/ → ready/as usual. A subtask never reachesdone/on its own — the epic gates that. - Integration. When the last subtask reaches
ready/: restart the project, refresh all data (re-run imports/migrations), and run the full test suite. - Hand-off. Only then move the epic card to
ready/. If valid authorization covers parent and childrendone, move parent first, then eligible subtasks; verifyepic/<ID>is clean before an authorized squash merge. Rename the archive todone/<ID>(git branch -m epic/<ID> done/<ID>) only after the merge succeeds and its result is verified; otherwise retainepic/<ID>and report that the cards remain on the task branch. Never delete it.
See reference.md for the full epic protocol.
Git Commits
Git mechanics follow the git-repo-run core. Kanban's delta: a task is worked in its own branch (an epic's subtasks share the epic branch — see Epics above).
- Branch. By default work the task in a NEW branch
task/<ID>(aligns with kanban-schedule-run). Create it at start. - Sub-agent commits. When local commits are authorized, each sub-agent commits only its own work, following the repository's message and trailer policy. Preserve another actor's staged changes.
- Normal local commits. Commit coherent, validated progress proactively
when useful; a separate user-approval gate is not required for ordinary local
task commits. At
test → ready, the orchestrator makes a verified wrap-up commit containing the latest card body and any remaining owned task files. Do not create an empty or redundant commit when that exact owned state is already committed and verified. - Authorized finalization. Review and gates OK → move the card to
done/and verify the branch is clean (git status --shortempty) only whendoneis authorized. If merge is separately authorized, only then squash-merge the branch into the default branch as ONE commit, verify the merge result, then rename the branch todone/<ID>— strip thetask/prefix (git branch -m task/<ID> done/<ID>); the archive isdone/<ID>, NOTdone/task/<ID>. Kept as an archive for optional later cleanup — do not delete immediately. If merge is not authorized or does not complete successfully, retain the task branch and do not archive-rename it. After any authorized push/deploy, read back the exact target and verify the expected remote revision/deployed version or state before reporting success. - Moving cards between stage dirs →
kanban-move.sh(uses the bundled Git-aware path helper, validates the transition); if a separate path operation is needed, ask the user to invokegit-path-runmanually.
See reference.md for the autonomous-run commit contract.
Stop Conditions
- Do NOT skip planning.
- Do NOT perform
done, merge, push, or deploy without valid authorization explicitly covering that action and target; do not ask again when a valid recorded grant already covers it. - Do NOT start a card from
grooming/— resolve open questions, move totodo/first. - Resolve routine grooming choices from the authorized context; ask when a material user choice or required authorization is missing, and record decisions.
- Do NOT move to
ready/while tests are red. - Do NOT fix out-of-scope findings solely because they are small. Search for a duplicate before any authorized card creation; otherwise report the finding.
Task Delegation Rules
- One agent — one zone. Cross-zone task: the main agent does its own zone; the shared contract lives in a separate skill (e.g. a protocol/contract skill); adjacent implementations are done by their own agents reading that same skill.
security-auditor— read-only: emits a report, writes no code. Fixes are done by an implementer agent.test-engineerwrites tests, not business logic. If a test needs a new endpoint/hook in the code → file a subtask in kanban and delegate it to an implementer agent.- New agent — only when clearly needed. If the task fits an existing agent — don't spawn extra agents.
Operations: decisions, lifecycle and handoff
Use for starting, moving, reviewing, or completing tasks on a project Kanban board. Resolve the board and its supported operations through the project or runtime interface; check current cards and project conventions before changing state.
Decisions
When a decision is needed, explain its operational consequence and present concrete choices in the same interaction. Recommend one option and its trade-off; use an available choice interface when appropriate. Record the accepted decision on the affected card before the dependent action. If an unanswered decision may be resolved by the runtime's best-judgment policy, choose a reversible option consistent with the actual instructions. See decision presentation when choosing the interaction.
Lifecycle
- Present a concise interactive read-back of purpose, acceptance criteria, approach, and affected areas before starting work.
- Follow the project's defined transitions. For the common workflow, preserve
todo → progress → test → ready → done; pause or cancel only through the supported project mechanism. - A task reaches
doneonly after explicit user approval for that task. Review approval, a profile name, credentials, or a successful gate do not supply that approval. - If the owner explicitly classifies a card as superseded, history-only, or merged into another card, record the decision and receiving card, including unique acceptance criteria, in both records before archiving it through the supported mechanism. Archival is not implementation completion.
- Add concise execution-log entries after material work, verification, operational actions, or blockers, using the language required by the project.
Deletion of operational data
Before a separately authorized destructive operation, establish the exact resource boundary, capture durable evidence, and independently verify its count and scope. Perform the narrow authorized deletion, recheck the target and adjacent protected resources, and record the outcome. Creating or moving a task does not authorize deleting its data.
Verification and handoff
Distinguish static validation, runtime validation, and full-suite results. Report unrelated failures with their owner, and never describe unrun checks as passed. At handoff, summarize verified evidence, remaining work, side findings, and deduplication results. Collect unrelated nits, errors, suspicions, and follow-up candidates; map each to an existing waiting card when possible and state its proposed placement and scope. An active task does not by itself authorize an unrelated card change: obtain explicit owner approval unless the user already requested it or provided a grant covering that change; record that authorization in the card's execution log.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

