Loading...
Loading...
Found 11 Skills
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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.
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.
Spec-driven development workflow manager. Use when: (1) creating a DRAFT spec from input files or raw ideas, (2) creating a chunk plan from a DRAFT spec, (3) implementing a DRAFT spec (DRAFT to IMPLEMENTED transition), or (4) managing spec state transitions. Triggers on "create spec", "draft spec", "implement spec", "chunk plan", "spec workflow", or references to *-spec.md files.
Create implementation plan documents with development phases, sequencing, and actionable tasks. Works through 3 phases (structure, approach, generation) following established feature development process. Use when creating plan.md documents from technical specs. Triggers on "create implementation plan", "plan this feature", "sequence the development".
Ming Court Code —— Standardize Claude Code development processes using the institutional framework of the Ming Dynasty court. Three-level adaptive modes: Oral Edict (rapid execution), Court Debate (structured solution), Morning Court (multi-agent parallel processing).
Full-process specification for software development, covering requirements analysis, design, pre-development, development, testing, and delivery, including review mechanisms, coding specifications and Git workflow
Start Task
Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.
When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.