boojack
3 verified skills6 total stars
syncing-linear
Syncs issue artifacts (definition, design, plan, execution) to Linear. Creates or updates a Linear issue with a summarized title and structured description, and uploads full artifacts as linked documents. Use after any pipeline stage to push current state to Linear. Also triggers on: "sync to linear", "push to linear", "create linear issue", "update the ticket", "track this in linear". Reads artifacts produced by defining-issues and executing-tasks.
testing2
defining-issues
Converts vague requests into precise issue definitions grounded in the codebase, then researches and designs a solution for complex tasks. Produces definition.md (always) and design.md (for L-scope). Use when an issue needs to be clarified, scoped, or prepared before implementation — such as unclear requirements, vague feature requests, ambiguous bug reports, or undefined scope boundaries. Also triggers on: "what should we build", "scope this", "write up an issue", "define the problem", "clarify requirements", "design this", "how should we build this", "research solutions", "design doc". For implementation after definition, see executing-tasks.
development2
executing-tasks
Plans and executes implementation from a defined issue. Reads definition.md (and design.md if present), breaks work into tasks, then executes each task with validation. Use when a definition exists in docs/plans/ and implementation work should begin. Also triggers on: "build it", "implement this", "execute the plan", "start implementing", "do the work", "plan and execute", "break this into tasks and build it". Requires definition.md from defining-issues. For L-scope, also requires design.md. For syncing results to Linear, see syncing-linear.
development2