Loading...
Loading...
Found 14 Skills
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Start Task
Implements approved specification proposals by working through tasks sequentially with testing and validation. Use when implementing changes, applying proposals, executing spec tasks, or building from approved plans. Triggers include "openspec implement", "implement", "apply change", "execute spec", "work through tasks", "build feature", "start implementation".
GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.
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.
When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.
현재 프로젝트의 확인된 요구사항을 실제 기능·화면·동작으로 구현하고 구현 범위에 맞는 기본 검사를 수행한다. “서비스 만들어줘”, “계속 개발해줘”, “다음 기능 구현해줘”, “이 자료대로 완성해줘”처럼 코드를 만들거나 변경하는 요청에 사용한다. 제품 방향 정의만, 샘플 데이터 생성만, 영구 데이터 연결만, 기존 문제 수정만, 검증만 또는 배포만 요청한 경우에는 사용하지 않는다.
Orchestrate the complete development workflow from ticket to PR. Use when: (1) Starting work on a JIRA ticket, (2) Following the planning-coding-review cycle, (3) Creating a PR after completing work, (4) Running code review before finalizing. This skill ties together workspace-manager, git-worktree, github, and jira skills into a cohesive workflow.
Use when setting up speckit (Specification-Driven Development) in a repo — copies slash commands, templates, and optionally creates a project constitution.
Phase 2 of the feature workflow —— Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and go back to discuss the plan instead of pushing forward blindly.
Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.
Carry an approved task through to working, verified code