Loading...
Loading...
Found 458 Skills
Create Linear issues. Use when creating bugs, tasks, or feature requests.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
This skill should be used when user asks about "Linear issues", "issue tracking best practices", "sprint planning", "Linear project management", or "creating Linear issues".
Use when you have specs or requirements for a multi-step task to break it down into detailed tasks, before executing it
Use this skill when the user wants to open, create, or manage projects across local macOS, Apple Containers, and Fly.io Sprites using the zp CLI.
Write Project Guardrails, i.e. project engineering specifications. Applicable scenarios: when you need to define frontend, backend, API, data, security, operation and maintenance, and release standards during new project launch, tech stack change, multi-team collaboration, incident review, or code specification drift.
Bidirectional sync between BMAD planning artifacts and GitHub Projects v2. Use this skill whenever the user says "sync to github", "push stories", "pull status from github", "set up github project", "github sync", "onboard github project", "create github issues from stories", "update stories from github", "sync status", or wants to manage BMAD artifacts in GitHub Projects. Also trigger when user mentions "gh project", "github board", "sprint board", "project roadmap", "relationship field", "blocked by", or "parent issue" in the context of BMAD artifacts. Trigger on implicit cues like "I want to track stories in github", "let's set up a project board", "what's out of sync", "push the sprint to github".
Use after planning completes and before any implementation begins. Verifies that the current phase contract, story map, and bead graph are structurally sound, execution-ready, and aligned with locked decisions. Use for prompts like "validate the plan", "is this ready to build?", "check the bead graph", "verify execution readiness", or whenever there is doubt about whether the current phase is safe to execute.
Plan and file goals and feature issues through conversation. Use when the user wants to create goals, plan features, file issues, or discuss what to build next.
Enter this sub-process when developing new features — turn the vague idea of "adding X capability" into a closed-loop acceptance process, with solution files archived so that both AI and users can later check what was thought and why decisions were made at that time. Trigger scenarios are focused on new capabilities ("develop new features", "add X", "implement XX") and do not address bugs in existing code. This skill only handles routing, deciding which next step to take among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Spade integration. Manage data, records, and automate workflows. Use when the user wants to interact with Spade data.
Interact with Dida365 Open API using Python CLI to manage TickTick tasks/projects, suitable for scenarios where you need to call TickTick APIs via scripts or command line (such as querying, creating, updating, completing, and deleting projects/tasks).