Loading...
Loading...
Found 81 Skills
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", "スキル開発ワークフロー", "スキルを作って公開", "新しいスキルを開発".
Bootstrap the openspec/ directory structure for Spec-Driven Development in any project. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
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".
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
Interactive onboarding workflow that interviews users to understand their coding goals and generates PR-ready implementation plans. Use when starting a new development task to ensure clear requirements and structured execution.
CX Workflow - Task Execution and Contract Validation. Triggered when users mention phrases such as "execute task", "start development", "implement feature", "write code", "continue working", "next task". It follows a 5-step process: Read Task → Implementation → Contract Validation → Testing → Submission. It uses local task-{n}.md and status.json files to automatically verify whether the implementation conforms to the contract. cx-summary will be automatically triggered after all tasks are completed.
Полный цикл разработки доработок 1С — от анализа до реализации с БСП compliance. 9 фаз: оценка, discovery, исследование, уточнение, проектирование, ревью плана, реализация, ревью кода, итоги.
Use when implementing features from a spec or requirements document, doing multi-phase work, or when you need structured Analyze-Plan-Ask-Execute-Review cycles to prevent ad-hoc coding and ensure spec-aligned, pattern-consistent implementations