SkillsAdd

lennney/ticketpilot · Archived

ticketpilot-product-boundary

Use when deciding project scope, prioritization, or whether a feature belongs in the TicketPilot MVP.

First seen Jun 19, 2026

Installation

$ npx skills add lennney/ticketpilot --skill ticketpilot-product-boundary
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

ticket-risk-policy Same source
lennney/ticketpilot

Use when implementing or reviewing risk assessment, human review routing, complaint handling, c…

1 installs
rag-evaluation Same source
lennney/ticketpilot

Use when modifying retrieval, chunking, RRF, rerank, citation, answer grounding, or evaluation …

1 installs
project-plan-audit Same source
lennney/ticketpilot

Use when auditing TicketPilot project plans, modules, tests, OpenSpec changes, and phase status…

1 installs
stop-that-shit Same author
lennney/stop-that-shit

Keep coding agents focused on requested and necessary work.

61 installs

Also in this package

Other skills from lennney/ticketpilot.

npx skills add lennney/ticketpilot
ticket-risk-policy 1 rag-evaluation 1 project-plan-audit 1

Browse all from lennney/ticketpilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch master
Open issues 3
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 902 B
  • docs SUMMARY.md 137 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

TicketPilot Product Boundary

TicketPilot is a Chinese customer support ticket triage and evidence-grounded reply Copilot.

Must preserve:

  • ticket normalization
  • intent classification
  • risk gate
  • FAQ / Policy / Case layered retrieval
  • hybrid retrieval
  • evidence-grounded draft reply
  • human review
  • trace
  • evaluation

First version should not include:

  • multi-agent role-play inside the product
  • model training
  • complex knowledge graph
  • voice support
  • multi-channel CRM integration
  • large-scale crawling
  • distributed microservices

Priority principle: If a feature does not improve workflow completeness, risk control, evidence traceability, human review closure, evaluation, or interview explainability, do not prioritize it.