Loading...
Loading...
Found 54 Skills
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.
Use when the user needs proposal/specs research artifacts produced for a Superspec (superspec-rpi) OpenSpec change.
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.
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
通过创建下一个产出物继续处理 OpenSpec 变更。当用户想要推进其变更、创建下一个产出物或继续其工作流程时使用。
Launch a new OpenSpec change using an experimental artifact workflow. Use this when users want to create new features, fixes or modifications through a structured step-by-step approach.
Interactively onboard a project to OpenSpec by running a structured interview and generating a complete QRSPI-configured openspec/config.yaml. Use this skill whenever a user mentions "openspec config", "config.yaml for openspec", "set up openspec", "onboard to openspec", "generate openspec config", "QRSPI config", or asks how to configure OpenSpec for their project — even if they just say "help me set up openspec" or "I want to use openspec". Always prefer this skill over ad-hoc config generation.
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".
Comet — OpenSpec + Superpowers Binary Star Development Workflow. Initiate with /comet, which automatically detects phases and distributes to subcommands. Five phases: Open → Deep Design → Plan & Build → Verify & Finalize → Archive.
Use when planning, applying, validating, or archiving OpenSpec changes in this repo, or when downstream AI tools need OpenSpec JSON status/instructions. NOT for generic code review, unrelated docs edits, or replacing generated upstream openspec-* skills.
Điều phối toàn bộ quy trình làm app Flutter bằng AI - từ đọc OpenSpec, quyết định có cần migration không, sinh code, chạy MCP auto-fix, xin duyệt UI, đến commit git. LUÔN dùng skill này đầu tiên khi user yêu cầu thêm/sửa tính năng cho app Flutter, kể cả khi họ chỉ nói ngắn gọn như "thêm màn hình đăng nhập" hay "làm app bán trà sữa". Đây là checklist điều phối, không tự viết 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.