メニュー
Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Check changelogs for Bevy, Next.js, Zustand, wasm-bindgen, Rapier, and all SpawnForge deps. Use when training data may be stale, before major upgrades, or when a library API behaves unexpectedly.
Forward-looking sister to changelog-review. Scans our SaaS + library stack (analytics, monitoring, observability, agent tracking, infrastructure, AI, payments, auth) against TODAY's provider changelogs / releases / betas to surface capabilities we are NOT yet using — newly shipped or long-available-but-unadopted — that could improve the product or our build harness. Every opportunity comes with its provider cost. Use for quarterly capability audits, when asking "what new features can we leverage," or before planning a growth/observability/infra initiative.
SpawnForge Stripe webhook patterns — idempotent refunds, CTE atomic claims, neonSql transaction ordering, token billing. Auto-loads when editing billing code.
Monitor open PRs for CI failures and review comments, then fix issues automatically. Use when PRs need to be driven to green — checks CI status, Sentry comments, merge conflicts, and applies fixes.
Review a PR for SpawnForge bugs, security issues, and regressions. Posts inline GitHub comments with severity markers. Use when asked to "review PR", "code review", or "check this PR". Invoke with /pr-code-review <PR number>.
Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria.
| name | kanban |
| description | Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria. |
| user-invokable | true |
Manage project work via the taskboard API at http://localhost:3010.
Project: SpawnForge (prefix: PF, ID: 01KMM9ZA6SBZ7RKJZJTZS9VR4R)
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /api/board | View full Kanban board |
| 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 |
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]
01KMR5E36TP59PRQA8GQEWJVM1), PM (01KMR5E3852BWXAZ219W47CSKS)in_progressdone when all acceptance criteria met