jpmschweitzerandClaude Fable 5
33c14531da
Live-command corrections (atlas corridor-status, real body-ID naming), failure-proofed glb-gen/sprite-gen render scripts, Trellis API reference extracted. image-gen: fixed the output-path bug and de-forked the local image_connector.py to the canonical tooling/db/ copy. ticket skill consolidated to point at ticket-cli.md (setparent-none fix applied there too). Part of T-1099. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
name, description, user-invocable, allowed-tools
| name | description | user-invocable | allowed-tools |
|---|---|---|---|
| ticket | Manage project tickets in the pql planning store — day-to-day ticket CLI (list, create, update, board, phase epics). Use when the user says "ticket", "create a ticket", "show tickets", "board", "phase epic", "what's in the active phase", or invokes /ticket. Wraps the pql CLI for structured project management. For changelog/planning-store internals (branch moves, recovery, write-through mechanics), use the pql skill instead. | true | Bash, Read, Grep, Glob |
Ticket Skill
Manage tickets via pql (.pql/pql.db, rebuilt from the git-tracked
.pql/changelog/). Ids are T-NNN (T-440 == legacy #440). Full command reference:
.claude/rules/ticket-cli.md.
Commands
List/show/create/update/dependencies/labels/refinement syntax is not
repeated here — see the full command reference linked above
(.claude/rules/ticket-cli.md), the one canonical copy.
Negative knowledge (not in the rule file): pql ticket list has no
--type/--priority filter — list and read the JSON, or use --under <epic> for an epic's subtree.
Phases (the cascade hierarchy, not labels or a milestone entity)
pql ticket list --under T-750 --unblocked # ready work in the active phase (currently T-750, Phase 4)
pql ticket setparent T-990 T-750 # put a ticket in the phase (re-parent)
pql ticket show T-745 --tree # the cascade: initiative -> 6 phase epics
The active phase is the in_progress phase epic under T-745 (sequential per D-166).
Workflow
- Decisions from
governance/records become initiatives - Initiatives break into epics (major work areas)
- Epics break into stories (user-facing deliverables)
- Stories break into tasks (concrete work items)
- Phase gating is the cascade hierarchy (initiative T-745 → six phase epics), not labels/milestones
/whats-nextselects the next batch viapql ticket list --under <active-phase-epic> --unblocked- Mutations flow to the git-tracked
.pql/changelog/; the pre-commit hook exports + stages it .pql/changelog/is write-through data — nevergit restoreor hand-edit it; for non-routine planning-store ops (branch moves, recovery) loadSkill(pql)first