choral-skills

Use when a maintainer explicitly asks for Knowledge Workflow setup, checks, upgrade migration, manifest work, or approved configuration updates.

Use when the user asks to implement an approved Kanban task or linked project change with clear acceptance criteria.

Use when delivery work needs a proposal before editing task candidates, Kanban cards, backlog shape, or board changes.

Use when delivery work needs review, a PR or local diff needs validation, or Done readiness is in question.

Use when a user asks how to use Knowledge Workflow in a repository, where content belongs, which skill applies, what project rules mean, how to recover safely, or how to record local workflow feedback.

Use when the user has approved a specific shared-knowledge write, promotion, reorganization, or update.

Use when an idea, requirement, feedback, research note, decision, or fact may become shared knowledge but the target is not yet approved.

Use when non-task knowledge needs a read-only check for schema, frontmatter, localization, links, or consistency.

Use when the user asks for a read-only summary of knowledge health, delivery progress, decisions, queues, ownership, blockers, or risks.

Use when the current member asks to manage or run their local WORKLIST, including run-next, run-loop, run-goal, plan-only, grooming, or logs.

Use when the user has approved adding, moving, or updating cards on the repository Kanban board.

Use when the user asks which accepted Kanban task to work on next and dependencies or readiness may affect the answer.

Use when task items or Kanban links need a read-only check for readiness, dependencies, issues, acceptance, or board consistency.

Use when converting local document files such as PDFs, Office documents, HTML, text, or other MarkItDown-supported inputs into Markdown.