GitHub
plan-task
체계적인 작업 계획 수립. 규모 판단 → 요구사항 명확화 → 사용자 여정 → 비즈니스 로직 순으로 진행합니다.
☆ 1View skill
Development AI Skills
Discover Development skills, compare source repositories and read the instructions for each workflow.
Categories: Development
Development Clear filters
Browse skills
GitHub
debug
에러를 분석하고 수정합니다. 에러 메시지나 로그를 입력하세요.
☆ 1View skill
GitHub
monitor
시스템 모니터링. 현재 상태를 확인하고 이상 징후를 탐지합니다.
☆ 1View skill
GitHub
incident
인시던트 대응 파이프라인. 복구 최우선으로 대응 → 복구 → 분석 순으로 진행합니다.
☆ 1View skill
GitHub
auto-dev
자동화된 개발 파이프라인 실행. 탐색 → 계획 → 구현 → 검증 → 리뷰 순으로 진행합니다.
☆ 1View skill
GitHub
db-query
Execute database queries using PostgreSQL MCP. Use when users want to run SQL queries, analyze data, check schema, or optimize queries.
☆ 1View skill
GitHub
infra
인프라 작업 파이프라인. 탐색 → 계획 → 구현 → 검증 → 적용 순서로 진행합니다.
☆ 1View skill
GitHub
deploy
배포 파이프라인. 검증 → 배포 → 모니터링 순서로 진행합니다.
☆ 1View skill
GitHub
requirement-traceability
Provides REQ-* key pattern definitions, validation rules, and traceability operations. Use for understanding requirement key formats, validating keys, or tracing requirements through the SDLC lifecycle.
☆ 1View skill
GitHub
extract-business-rules
Extract business rules (BR-*) from requirements - validation rules, business logic, error handling, and decision criteria. Use when disambiguating requirements to identify specific rules that can be autogenerat...
☆ 1View skill
GitHub
commit-with-req-tag
Create final git commit with requirement traceability tags (REQ-*). Use after refactor-phase to finalize TDD cycle with proper requirement linkage for bidirectional traceability.
☆ 1View skill
GitHub
implement-step-definitions
Implement step definitions for Gherkin scenarios, translating Given/When/Then into executable test code. Use after write-scenario when scenarios are defined but step definitions are missing.
☆ 1View skill
GitHub
green-phase
Implement minimal code to make failing tests pass (GREEN phase of TDD). Write just enough code to pass tests, no more. Use after red-phase when tests are failing.
☆ 1View skill
GitHub
run-integration-tests
Run integration tests validating cross-component requirements and system behavior. Executes BDD scenarios, API tests, and end-to-end tests. Use to validate integrated system or as pre-deployment quality gate.
☆ 1View skill
GitHub
trace-production-issue
Trace production alerts and issues back through REQ-* to original intent, creating new intent for remediation. Closes feedback loop from Runtime → Intent. Use when production alerts fire or issues discovered.
☆ 1View skill
GitHub
create-observability-config
Setup observability platform configuration (Datadog, Prometheus, Splunk) with REQ-* dashboards and alerts. Creates monitors for each requirement with SLA tracking. Use when deploying to production or setting up...
☆ 1View skill
GitHub
autogenerate-from-business-rules
Autogenerate production code from disambiguated business rules (BR-*). Converts BR-* specifications into validators, constants, and logic. Use when requirements have been disambiguated into BR-*, C-*, F-* forma...
☆ 1View skill
GitHub
refine-requirements
Refine requirements from discoveries during TDD/BDD implementation. Captures edge cases, race conditions, and business rules discovered by developers. Enables requirements refinement loop. Use when developers d...
☆ 1View skill
GitHub
extract-constraints
Extract technical constraints (C-*) from ecosystem E(t) - timeouts, API limits, compliance requirements, platform dependencies. Acknowledges given constraints, not design choices. Use to document ecosystem real...
☆ 1View skill
GitHub
autogenerate-validators
Autogenerate validation functions from business rules (BR-*) that specify formats, patterns, ranges, or constraints. Use when BR-* includes validation specifications like regex patterns, min/max values, or allo...
☆ 1View skill
GitHub
design-with-traceability
Create technical solution architecture from requirements with REQ-* traceability. Designs components, APIs, data models, and interactions. Tags all design artifacts with requirement keys. Use after requirements...
☆ 1View skill
GitHub
create-adrs
Create Architecture Decision Records (ADRs) documenting strategic technical decisions while acknowledging ecosystem E(t) constraints. Use when choosing cloud providers, languages, frameworks, databases, or arch...
☆ 1View skill
GitHub
check-requirement-coverage
Homeostatic sensor detecting requirements without implementation or test coverage. Scans for REQ-* keys in requirements docs and checks if they have corresponding code and tests. Use to find coverage gaps.
☆ 1View skill
GitHub
bdd-workflow
Complete Behavior-Driven Development workflow coordinating SCENARIO → STEP DEFINITIONS → IMPLEMENT → REFACTOR cycle with Given/When/Then scenarios. Use when writing BDD tests or implementing features from user...
☆ 1View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.