lennney/ticketpilot

project-plan-audit

Use when auditing TicketPilot project plans, modules, tests, OpenSpec changes, and phase status before continuing development.

phase-acceptance-gate

Use after every implementation batch to produce a strict acceptance report with requirement-to-evidence mapping.

project-change-log

Use after every meaningful feature, bug fix, architecture decision, evaluation update, prompt change, or skill change.

rag-evaluation

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

secure-coding

Use when adding API providers, environment variables, external services, logs, deployment configs, or documentation that may expose secrets.

spec-driven-development

Use when planning or implementing any non-trivial TicketPilot change. Requires proposal, design, tasks, acceptance criteria, and validation before implementation.

ticket-risk-policy

Use when implementing or reviewing risk assessment, human review routing, complaint handling, compensation handling, legal risk, privacy risk, or account security risk.

ticketpilot-product-boundary

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