Loading...
Loading...
Found 132 Skills
一个全面、结构化的特性开发工作流程，包含代码库探索、架构设计、质量审查和实现等专门阶段。在构建需要以下条件的新特性时使用：（1）在做出更改之前了解现有代码库，（2）通过系统性的提问澄清模糊的需求，（3）在实现之前设计周到的架构，（4）通过多维度的代码审查确保质量。非常适合涉及多个文件、需要架构决策、包含复杂集成或需求有些不明确的功能特性。
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
Use when annotating code with structured metadata, tags, and markers for AI-assisted development workflows. Covers annotation formats, semantic tags, and integration with development tools.
Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
Use when coordinating software development projects requiring multiple specialists (architect, developers, mathematician, statistician, notebook-writer) with quality gates for archival setup, requirements, architecture, pre-mortem, code review, testing, and version control integration.
Orchestrate the full skill development lifecycle from idea to publication. Guides through ideation, requirements definition, skill implementation, and marketplace registration. Use when: "create a new skill end-to-end", "skill development workflow", "build and publish a skill", "スキル開発ワークフロー", "スキルを作って公開", "新しいスキルを開発".
Structured development workflow that separates research, planning, and implementation into distinct phases with persistent markdown artifacts. Use when starting any non-trivial feature, refactor, bug investigation, or codebase change. Trigger on: "deep work", "research and plan", "plan before coding", "write a plan", "research this codebase", "don't code yet", "understand then implement", or when the user wants a disciplined approach to a complex task. Also use when the user says "research", "plan", "annotate", "implement the plan", or references research.md/plan.md artifacts.
Orchestrate the 9-step skill development lifecycle for the CaldiaWorks Skills repository. Guides through ideation, issue creation, planning, branch creation, requirements definition, skill implementation, commit, pull request, and post-merge issue cleanup. Use when: skill development workflow, develop a skill end-to-end, skill-dev-workflow, /skill-dev-workflow, create and publish a skill.
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Orchestrate full development workflow. Use when implementing features, starting structured development, or user mentions "workflow" or "implement issues".
Use this when you have a written implementation plan and execute it in separate sessions with review checkpoints