Tristan578

kanban

"Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria."

Tristan578 9 1 Updated 4mo ago
GitHub

Install

npx skillscat add tristan578/project-forge/kanban

Install via the SkillsCat registry.

SKILL.md

Taskboard Management Protocol

Manage project work via the taskboard API at http://localhost:3010.

Project: SpawnForge (prefix: PF, ID: 01KMM9ZA6SBZ7RKJZJTZS9VR4R)

API Endpoints

Method Endpoint Purpose
GET /api/board View full Kanban board (optionally scoped with ?projectId=...)
GET /api/tickets?project=...&status=... List tickets with filters
GET /api/tickets/{id} Get ticket details
POST /api/tickets Create ticket (requires projectId, title)
PUT /api/tickets/{id} Update ticket fields
POST /api/tickets/{id}/move Move ticket (body: {"status": "done"})
DELETE /api/tickets/{id} Delete ticket
POST /api/tickets/{id}/subtasks Add subtask (body: {"title": "..."})
POST /api/subtasks/{id}/toggle Toggle subtask completion

Mandatory Ticket Template

Every ticket description MUST include:

**User Story:**
As a [persona], I want [specific goal] so that [measurable benefit].

**Description:**
[Technical context, affected files, scope boundaries]

**Acceptance Criteria:**
- Given [precondition], When [action], Then [expected result]  (happy path)
- Given [precondition], When [action], Then [expected result]  (edge case)
- Given [precondition], When [action], Then [expected result]  (negative/error)

Validation Rules

  1. User Story — Must match regex As an?\s+.+,\s+I want\s+.+\s+so that\s+.+ (case-insensitive)
  2. Description — Technical context (at least 20 chars beyond user story + AC sections)
  3. Acceptance Criteria — Given/When/Then format, minimum 3 scenarios (happy/edge/negative)
  4. Priority — Must be set: urgent, high, medium, or low
  5. Team — Must be assigned: Engineering (01KMR5E36TP59PRQA8GQEWJVM1), PM (01KMR5E3852BWXAZ219W47CSKS)
  6. Subtasks — At least 3 implementation steps before work begins

Workflow

  1. Check board state before starting work
  2. Pick or create a ticket
  3. Move to in_progress
  4. Toggle subtasks as you complete them
  5. Move to done when all acceptance criteria met