Essential command-line tools and system utilities.
Figma design system integration with API automation, design tokens, and component libraries for scalable design infrastructure. Enhanced MCP integration, error handling, and performance optimization.
When the user asks about ClickUp synchronization or syncing roadmaps with ClickUp
This skill conducts structured interviews to gather requirements. Auto-triggers when requirements are unclear, ambiguous, underspecified, when multiple valid approaches exist, when scope is undefined, or when Claude needs user input before proceeding. Use for discovery, clarification, decision-making, and stakeholder alignment.
ALWAYS apply this skill for ANY software development task. Triggers: implement, create, build, add, write, code, function, class, component, API, feature, fix, bug, debug, refactor, improve, clean, review, check, design, architect, structure, test, endpoint, module, service, handler, controller, model, schema, migration, deploy, configure. This skill enforces kadoppe's development principles for all coding work.
Auto-update ROADMAP.md status based on completed features. LOAD THIS SKILL WHEN: User says "更新 roadmap", "完成功能", "里程碑" | features completed | planning new milestones | before releases. CAPABILITIES: Status marking (📋→🚧→✅), auto-detect from commits, suggest additions for unlisted features.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Route-aware gap analysis. For Brownfield - uses /speckit.analyze to compare specs against implementation. For Greenfield - validates spec completeness and asks about target tech stack for new implementation. This is Step 4 of 6 in the reverse engineering process.
Complete feature development workflow orchestrating multiple skills from planning to deployment. Triggers: FD, 新功能, 開發功能, feature, implement, 實作, 實現, 建立功能, create feature, develop, 開發新, add feature, 加功能, 功能開發.
Generates session summaries and resume prompts for multi-session work. Use when completing features, before context limits (~50% capacity), or when user says "summary", "wrap up", "save progress", "end session". Creates markdown in docs/summaries/ with completed work, files modified, and restart instructions.
Bulk-complete tasks/steps in a project. Load when user says "bulk complete [project]", "mark all done", "complete phase X", or needs to finish project tasks efficiently. Works with both steps.md and tasks.md formats.
Podcast production patterns and workflows. Use when recording podcasts, editing audio, transcribing episodes, generating show notes, RSS feed management, or podcast distribution.
Manages the Anubis Issue Tracker GitHub project board. Use when you need to organize issues by difficulty/status, move issues through workflow stages, or generate board status reports.
EXAMPLE - Workflow for processing large Things3 inboxes using LLM-driven confidence matching and intelligent automation. This is a genericized example - create your own version in inbox-processing/ for personal use.
Use when tracking Beads epic status, syncing progress to GitHub/Shortcut, generating dependency diagrams, or monitoring multi-repo work. Bridges Beads issue tracking with project management tools.
File-based task management with shai-tix CLI. Use when user mentions kanban, ticket, planning, task tracking, or references tickets by [id] or #id format. MUST run via: uvx --from shai-tix==0.1.3 shai-tix <cmd>. Data stored in .tix/ directory (NOT .shai-tix/).
Enforce branch-based workflow with draft PRs for emoji_gen. Use when starting new work, creating branches, or opening pull requests. Mentions of "new feature", "bug fix", "start work", "create PR", or "pull request" should trigger this Skill.
Generate comprehensive pull request descriptions with summaries and test plans. Use when creating PR descriptions or documenting code changes.
Automatically submit pull requests with full autonomous workflow. Use when the user mentions creating a PR, submitting a PR, merging changes, opening a pull request, or wants to get their changes reviewed. Also use when code changes are complete and ready for review.
RESTful API design principles, patterns, and best practices. Use when building backend APIs. (project)
Generate a detailed task completion report for any milestone spec, showing overall completion percentage, per-phase breakdown with progress bars, and status indicators. Invoked when user asks for progress tracking, phase summaries, completion reports, or needs to assess work status before PR/merge.
