Loading...
Loading...
Found 62 Skills
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
Start working on a PRD implementation
Get up to speed on the current branch's intent by analyzing commits, changes, and optionally a Linear ticket. Use when starting work on an existing branch.
Create feature branches linked to issues with consistent naming conventions. Generates branch names from issue numbers and descriptions, creates the branch, and checks it out. Use when: create branch, new branch, feature branch, branch for issue, start working on issue, branch-create, /branch-create.
Use when you need to locate the current spec pack (FEATURE_DIR) in the Spec process of sdlc-dev, avoid reading or writing requirements/*.md in the wrong directory, or encounter issues such as "misreading context/writing to the wrong file/non-compliant branch".
Generate changelog entries for code changes.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - Guides the completion of development work by providing packaged options for merging, PR, or cleanup
Fetches Jira ticket context, creates a branch, and drafts an implementation plan
Enforces safe deployment practices. Use before any production deploy to prevent overwriting newer code. Activated when deploying, pushing to production, or running deploy commands.
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Use when completing work on a feature branch, preparing to merge, or cleaning up after development is done. Triggers: branch work is complete, user says "merge", "create PR", "finish branch", "done with this branch", ready for code review.
Use when ALL tasks in an epic or branch are closed and you are ready to integrate the entire body of work - never after individual task completions, never mid-epic