prd-to-tickets
PRD to Tickets
Break a PRD into independently-grabbable Linear tickets using vertical slices (tracer bullets).
Process
1. Locate the PRD
Ask where the PRD lives (doc URL, markdown file path, GitHub issue/PR, Notion page, or pasted text).
If the PRD is not in context, fetch or read it first.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand current constraints and integration points.
3. Draft vertical slices
Break the PRD into tracer-bullet slices. Each slice should be a thin end-to-end path through all layers, not a horizontal layer-only task.
More from ajoslin/dot
pinescript
Use when creating or reviewing TradingView Pine Script v6 indicators/strategies/libraries, applying non-repainting best practices, generating Pine Script from other languages, or running Pine Script linting.
51session-export
Update GitHub PR or GitLab MR descriptions with AI session export summaries. Use when user asks to add session summary to PR/MR, document AI assistance in PR/MR, or export conversation summary to PR/MR description.
21find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
20vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with
19kimaki-expert
Provide expert support for Kimaki setup, Discord bot wiring, OpenCode session orchestration, slash-command troubleshooting, and automation workflows. Use when users mention Kimaki, kimaki.xyz, Discord-controlled coding agents, or channel-to-project mapping.
18init-review-policy
Initialize repo-scoped code review policy files under .opencode/review. Use when setting up project-specific review rules for /code-review.
18