the-rabak/focused-ticket-priming
portable/compound-engineering/skills/focused-ticket-priming/SKILL.md
Package one plan execution packet into a compact ticket-local execution packet with parent refs, scope fences, feature-home ownership, and evidence commands. Use when converting plans into local tickets or when execution needs one ticket-sized context pack without the full plan.
$ install --global
skillsauthnpx skillsauth add the-rabak/compound-engineering-plugin focused-ticket-primingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 6, 2026, 4:27 AM106.5s1 file scanned
SKILL.md
- name:
- focused-ticket-priming
- description:
- >-
- user-invocable:
- false
- model:
- openrouter/moonshotai/kimi-k2.6
Focused Ticket Priming
Turn one execution packet into one execution-ready ticket without dragging the whole plan into the ticket body.
Required contract
Before packaging a ticket, load commands/workflows/references/ticket-execution-contract.md (or the platform-local equivalent), quote its first non-empty line, and use it as the output contract.
If the contract cannot be loaded, stop instead of inventing a ticket shape.
Workflow
- Read the source packet, the plan WHY artifacts, the architecture handoff, and the resolved TDD/evidence contract.
- Keep the three context tiers separate:
- global guardrails stay global
- architecture and supporting docs stay on-demand
- only the smallest safe execution packet goes into the ticket
- Write the ticket using the exact frontmatter and section order from
ticket-execution-contract.md. - Preserve feature-home ownership, scope fence, parent refs, dependency type, and evidence command exactly.
- If the source packet is too vague to produce a compact ticket without guessing, stop and send the workflow back to
/deepen-plan.
Compactness rules
- Keep the
## Local Contextsection short enough for one focused execution run. - Embed only the files, interfaces, contracts, and WHY details that matter for this ticket.
- Link deeper design context through
## Deeper-Dive Refsinstead of copying it. - Surface visible uncertainty instead of pretending the packet is settled.
- Size by coupling and boundary clarity, not by file-count symmetry.
Ticket quality bar
A primed ticket is acceptable only when it:
- delivers one honest outcome
- preserves the source packet's WHY tracing
- keeps business logic in the declared feature home unless the architecture handoff justifies shared/global extraction
- includes a real validation command
- gives
/workflows:workenough local context to execute one ticket safely
Guardrails
- Do not expand a thin packet into a mini-plan.
- Do not remove parent refs just because the local context feels sufficient.
- Do not hide blockers or split dependencies across vague prose.
- Do not merge multiple outcomes into one ticket merely to reduce file count.
Related Skills
the-rabak/html-artifact-mutator
development
VerifiedTrustedCommunity
Mutates a single field or content region of an existing self-contained HTML artifact in place (island-first, no-added-facts, injection-safe) without regenerating the document from scratch. Invoked by a workflow command whenever it needs to back-write into an artifact it already composed -- e.g. a ref/status update, or a content rewrite that must re-project the affected view -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-composer
development
VerifiedTrustedCommunity
Composes a self-contained, interactive HTML artifact (island-first, single file, token-layer themed, injection-safe) from a workflow command's structured plan payload. Invoked by a workflow command at its artifact-write step -- currently `/workflows:plan` -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-mutator
development
VerifiedTrustedCommunity
Mutates a single field or content region of an existing self-contained HTML artifact in place (island-first, no-added-facts, injection-safe) without regenerating the document from scratch. Invoked by a workflow command whenever it needs to back-write into an artifact it already composed -- e.g. a ref/status update, or a content rewrite that must re-project the affected view -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-composer
development
VerifiedTrustedCommunity
Composes a self-contained, interactive HTML artifact (island-first, single file, token-layer themed, injection-safe) from a workflow command's structured plan payload. Invoked by a workflow command at its artifact-write step -- currently `/workflows:plan` -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026