feature-implementation
Skill for implementing features based on documentation, bridging technical specs (API, ERD, Stories) and code using a Test-Driven Approach.
Skill for implementing features based on documentation, bridging technical specs (API, ERD, Stories) and code using a Test-Driven Approach.
Create or update a structured plan directory with a PLAN.md index and numbered task files (001-*.md) containing checklists, tests, and completion criteria.
Prepare board meeting decks, updates, and materials for effective governance
Mark a plan as completed and archive it. Use this when you've finished implementing all items in a plan document.
Enterprise Skill for advanced development
Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.
Document root cause analysis for team learning. Blameless, actionable, preventive.
Create comprehensive project plans with timelines, dependencies, and resource allocation
This skill should be used when the user has a large, complex task requiring: (1) multi-file or multi-step implementation, (2) major refactoring or architecture changes, (3) new feature spanning multiple components. This skill should NOT be used for simple fixes, single-file edits, or quick questions. Activates strict verification with planning, success criteria, and evidence collection.
You are a relentless and effective Project Shipper, also known as a Project Manager or a Delivery Lead. Your superpower is getting projects over the finish line. You are an expert at planning, communication, and removing roadblocks. You are the ultimate owner of the project timeline and are accountable for its successful delivery.
This skill should be used when the user asks to "prioritize requirements", "prioritize epics", "prioritize stories", "prioritize tasks", "prioritize backlog", "use MoSCoW", "apply MoSCoW priorities", "assign priorities", "set priority labels", "rank features", "what should I build first", "what's most important", "order by importance", "must have vs should have", or when they need to determine the priority order of epics, user stories, or tasks using the MoSCoW framework.
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
Create a new Jira ticket. Use when the user wants to create a task, bug, story, or any other issue type in Jira.
Facilitate productive team retrospectives with structured formats and actionable improvement outcomes
MANDATORY - INVOKE IMMEDIATELY after completing ANY development task (feature, bug fix, refactor, maintenance). Creates SR-PTD documentation for future skill extraction. This is NOT optional - every task MUST have documentation.
Sessionary 프로젝트의 코딩 표준과 개발 가이드를 제공하는 skill. 사용자가 (1) 코드를 작성하거나 수정할 때, (2) 테스트를 작성할 때, (3) 프론트엔드/백엔드 개발 패턴을 물을 때, (4) TDD 개발을 진행할 때 사용. file types,or tasks that trigger it.
MMI評価エージェント - Modularity Maturity Indexによるモジュール成熟度評価(Cohesion/Coupling/Independence/Reusability)。/evaluate-mmi [対象パス] で呼び出し。
Extracts work units from plan artifacts and creates sequenced GitHub issues. Use when (1) decomposing plan.md into actionable issues, (2) creating issues with validation checklists, (3) linking issue dependencies, or (4) executing after /plan command completion.
Guidelines for planning engineering tasks with precision and clarity. Use this skill when creating todo lists, breaking down complex engineering tasks, or designing implementation plans for software development work. Emphasizes concrete, actionable steps without time estimates.
Use when user wants to assess progress toward an open-ended goal by reading and summarizing all iteration journals
Use when planning new features, starting spec-driven development workflows, or when the user mentions OpenSpec, SDD, or spec-driven development. Also triggers when user asks about feature specifications, change proposals, or wants to organize development workflow.
Analyzes and documents requirements for any software project, technology-agnostic approach to requirement engineering
Brief description of what this Skill does and when to use it (project)