mikeparcewski/task-management
skills/kanban/SKILL.md
Persistent task management through kanban boards with cross-session tracking. Provides guidance for using wicked-garden:kanban for CRUD operations, dependencies, priorities, and sprint management. Use when: "track tasks", "create a task", "add a todo", "manage tasks", "show my tasks", "what should I work on", "move task to done", "update task status", "kanban board", "project management"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden task-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:58 AM5.6s7 files scanned
SKILL.md
- name:
- task-management
- description:
- |
- Provides guidance for using wicked-garden:
- kanban for CRUD operations, dependencies,
- Use when:
- track tasks", "create a task", "add a todo", "manage tasks",
- disable-model-invocation:
- true
Task Management with Wicked Kanban
Persistent task management through Python scripts and a web UI, providing visual kanban boards and cross-session task tracking.
Overview
Wicked Kanban provides AI-native task management that persists across Claude Code sessions. Use the kanban.py script via Bash for CRUD operations, and the web UI for visual management.
Key benefit: Tasks created with TodoWrite are automatically synced to the kanban board via PostToolUse hook, but using the kanban script directly provides richer features (dependencies, priorities, sprints).
Using the Kanban Script
The script is located at ${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py. Execute commands via Bash.
Viewing Tasks
List all projects:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" list-projects
Get full project state (swimlanes + tasks):
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" get-project PROJECT_ID
Creating Tasks
Create a project first:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" create-project "Project Name" -d "Description"
Create a task (need swimlane_id from project):
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" create-task PROJECT_ID "Task Name" SWIMLANE_ID -p P1 -d "Description"
Priority levels: P0 (Critical), P1 (High), P2 (Normal), P3 (Low)
Updating Tasks
Update task status (move to different swimlane):
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" update-task PROJECT_ID TASK_ID --swimlane NEW_SWIMLANE_ID
Update task priority:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" update-task PROJECT_ID TASK_ID --priority P0
Comments and Commits
Add comment to task:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" add-comment PROJECT_ID TASK_ID "Comment text"
Link commit to task:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" add-commit PROJECT_ID TASK_ID abc123
Searching
Search tasks across projects:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" search "search query"
Search within a specific project:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" search "search query" --project PROJECT_ID
Scoped Boards
Four board types with purpose-built column schemas:
| Board Type | Terminal Column | Best For |
|------------|----------------|----------|
| crew (default) | done (Done) | Software development, crew phases |
| jam | jam:decision_made (Decision Made) | Brainstorming, design decisions |
| collaboration | collab:complete (Complete) | Cross-team workflows |
| issues | done (Done) | Bug tracking, general issues |
Create a typed initiative with --board-type:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/kanban/kanban.py" create-initiative PROJECT_ID "API Design" --board-type jam
# or: /wicked-garden:kanban:initiative create "API Design" --board-type jam
Filter board-status: /wicked-garden:kanban:board-status --board-type jam
Reaching a terminal column on jam or collaboration boards auto-writes a wicked-garden:mem record (decision or finding). Crew and issues boards do not trigger mem writes.
See refs/scoped-boards.md for full column schemas, provisioning rules, and CLI examples.
When to Use Script vs TodoWrite
Prefer Kanban Script For
- Tasks that should persist across sessions
- Work items requiring priorities or organization
- Tasks the user wants to track visually on the board
- Project-level task management
TodoWrite Still Works
TodoWrite calls are automatically synced to a "Claude Tasks" project on the kanban board via the PostToolUse hook. Tasks are organized into session-based sprints for better organization.
Use /wicked-garden:kanban:name-session "Feature Name" to name the session sprint. Each session gets its own sprint for easy filtering.
Web UI
Access the visual kanban board at http://localhost:18888. The web UI provides:
- Drag-and-drop task management
- Visual dependency graphs
- Sprint planning views
- Search across all projects
The server auto-starts with the Claude Code session. To start manually:
cd "${CLAUDE_PLUGIN_ROOT}" && uv run wicked-garden:kanban
Workflow Example
See refs/workflow-patterns.md for complete workflow examples (feature dev, bug fix, session resume).
Quick Reference
| Action | Command |
|--------|---------|
| List projects | list-projects |
| Get project | get-project PROJECT_ID |
| Create project | create-project "Name" -d "Desc" |
| Create task | create-task PROJECT_ID "Name" SWIMLANE_ID |
| Update task | update-task PROJECT_ID TASK_ID --swimlane ID |
| Add comment | add-comment PROJECT_ID TASK_ID "Text" |
| Link commit | add-commit PROJECT_ID TASK_ID HASH |
| Add artifact | add-artifact PROJECT_ID TASK_ID "Name" --type file |
| Project comment | add-project-comment PROJECT_ID "Text" |
| Search | search "query" |
| Create initiative | create-initiative PROJECT_ID "Name" --board-type jam |
| List initiatives | list-initiatives PROJECT_ID --board-type jam |
Additional Resources
refs/api-reference.md— Core script commands (projects, tasks, initiatives, search)refs/api-advanced.md— Advanced features (sprints, artifacts, data model)refs/scoped-boards.md— Full column schemas, provisioning, wicked-garden:mem triggersrefs/workflow-patterns.md— Common workflow examples (feature dev, bug fix, session resume)refs/advanced-patterns.md— Sprint planning, dependency graphs, priority filteringexamples/feature-workflow.md— End-to-end feature development workflow example
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026