task-planning
Use when creating task documents - generates TASK.md skeletons with metadata and acceptance criteria
Use when creating task documents - generates TASK.md skeletons with metadata and acceptance criteria
Use when sharing development progress publicly. Covers progress sharing, changelog writing, social media updates, community engagement, and milestone announcements.
Analyze mistakes with conversation length as potential cause (CAT-specific)
Execute backend implementation with TDD (Test-Driven Development). Write failing test first, then implement, verify each step. Use this skill when: - User asks to "implement this backend task", "implement backend" - Have an implementation plan ready and need to execute it - Executing steps from /backend.plan output - User says "start coding backend", "write backend code" - User asks to "use TDD", "write test first", "test-driven" for backend code - Fixing backend bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/backend/tasks/ (use /backend.tasks first if not exists) - MUST read constraints.md before writing any code. Flow: Check Task File → Read Constraints → TDD Cycle (RED→GREEN→REFACTOR) → Verify Each → Run All Tests → Update Task Status → Notify PM
Define SLIs, SLOs, and implement burn-rate alerting
Naming conventions for planning documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs or research reports, (3) questions about document organization in prompts/.
This skill should be used when managing project dependencies including safe updates, security audits, and compatibility analysis.
Create and manage support tickets throughout their lifecycle
Resume work on a project - discover state, verify health, clean up stale docs, suggest next tasks. Use when: (1) starting work at beginning of day, (2) after a long agent work loop completes, (3) user asks "what's next?", "what should we work on?", or similar, (4) user explicitly runs /next.
Use this skill when working with Keiai's 4-stage development workflow (Analysis, Planning, Solutioning, Implementation). This skill provides knowledge about the BMAD-METHOD inspired development process and how Keiai orchestrates autonomous development.
When you are asked to solve a issue with asana link given, consider this skill
Create a new feature in the backlog with proper structure
Groom the Jira backlog by closing completed tickets, removing redundant/stale tickets, reprioritizing, and assigning agents
This skill should be used when the user asks to "collect Linear activity", "generate Linear report", "show my Linear issues", "what did I work on in Linear", or requests activity summaries from Linear for specific date ranges. Provides workflow for collecting issues, projects, and cycles via Linear MCP.
Project Manager role: PMBOK 7/8 (8 Performance Domains, 12 Principles), PM tools (Jira, ClickUp, Linear, GitHub Projects, Azure DevOps), risk/schedule/cost management, EVM, agile ceremonies, dashboards, AI in PM, hybrid delivery. 38 methodologies.
Phase 기반 기능 계획 생성 skill. Quality Gate와 점진적 전달 구조 포함. 사용 시기: (1) 기능 계획 수립 시 (2) 태스크 분해 시 (3) 로드맵 작성 시 (4) 개발 전략 수립 시 (project)
👥 Comprehensive volunteer program management including recruitment, training, scheduling, and recognition for successful festival operations.
Structured iOS UX/UI review checklist. Use to critique hierarchy, spacing, affordances, copy, and states and output prioritized fixes (platform guidance, not implementation).
데이터 기반으로 한 주를 회고하고, 인박스 제로 및 액션 아이템 추출을 자동화하는 주간 리뷰 워크플로우입니다.
Analyze requirements and decompose complex work into atomic, dependency-aware GitHub Issues with proper priorities, test strategies, and implementation plans
Expert knowledge for running winter festival operations (Security, Marketing, CX, Lost & Found).
Use when creating epic structure - generates Epic INDEX.md with Kanban folders
Creates Features following the T-Minus-15 process template. Features represent significant deliverables that contain multiple User Stories. Includes proper metadata, MoSCoW prioritization, effort estimates, deliverables, and benefit hypothesis.