Loading...
Loading...
Found 53 Skills
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas and create change structure (proposal + design + tasks) via OpenSpec.
Create structured change proposals and specification differences using an OpenSpec specification-driven approach. It is used for feature planning, proposal creation, specification writing, introducing new capabilities, or initiating development processes. Trigger words include "openspec proposal", "planning", "create proposal", "plan change", "specify feature", "new feature", "new characteristic", "new requirement", "add feature planning", "design specification"
Apply OpenSpec OPSX in a strict one-task-at-a-time loop. Use when the user asks to execute work as single-task changes, wants spec-first implementation per task, or says to use OpenSpec method for each task from a task list. Supports both native /opsx command environments and manual fallback by creating OpenSpec artifact files directly.
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.
Generate comprehensive OpenSpec specifications directly from the current project state. Use when the user wants to create or populate main specs by analyzing existing code, documentation, AGENTS.md, GitHub issues, and pull requests — without going through the change/proposal workflow. Ideal for bootstrapping specs on a project that already has working code but no specs yet, or for refreshing specs to match the current implementation.
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Xử lý khi Data Model trong delta spec của OpenSpec (openspec/changes/<change-name>/specs/) thay đổi so với spec đã archive (openspec/specs/) - thêm/xóa/sửa field, đổi kiểu dữ liệu - để tránh crash do local database (Hive/SQFLite/Drift) hoặc parse JSON API bị lệch schema cũ. LUÔN dùng skill này TRƯỚC KHI sinh code, ngay khi phát hiện Data Model mới khác với model hiện có trong code.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Use when implementing a planned OpenSpec change by applying tasks and validating all artifacts.
Conversational SDD (Specification-Driven Development) guidance skill based on OpenSpec. It is automatically triggered when a user describes development requirements, and guides the user through the entire SDD process via conversations without any manual command input.
This is intended for use when OpenSpec workflows require dependency-aware parallel subagents that are compatible with OPSX commands, legacy OpenSpec commands, and Codex CLI prompt aliases.