Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
원문 언어: 영어
메뉴
SkillsMP는 shinpr/claude-code-workflows에서 47개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 47개 중 40개를 표시합니다.
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
원문 언어: 영어
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
원문 언어: 영어
Design Doc compliance and security validation with optional auto-fixes
원문 언어: 영어
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
원문 언어: 영어
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
원문 언어: 영어
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
원문 언어: 영어
Design Doc compliance and security validation with optional auto-fixes
원문 언어: 영어
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
원문 언어: 영어
Design Doc compliance and security validation with optional auto-fixes
원문 언어: 영어
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
원문 언어: 영어
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
원문 언어: 영어
Design Doc compliance and security validation with optional auto-fixes
원문 언어: 영어
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
원문 언어: 영어
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
원문 언어: 영어
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
원문 언어: 영어
Investigate problem, verify findings, and derive solutions
원문 언어: 영어
Execute materialized frontend task files in autonomous execution mode
원문 언어: 영어
Create frontend work plan from design document and obtain plan approval
원문 언어: 영어
Execute materialized task files in autonomous execution mode
원문 언어: 영어
Execute materialized frontend task files in autonomous execution mode
원문 언어: 영어
Create frontend work plan from design document and obtain plan approval
원문 언어: 영어
Execute materialized fullstack task files with layer-aware agent routing
원문 언어: 영어
Orchestrate full-cycle implementation across backend and frontend layers
원문 언어: 영어
Orchestrate the complete implementation lifecycle from requirements to deployment
원문 언어: 영어
Create work plan from design document and obtain plan approval
원문 언어: 영어
Execute materialized task files in autonomous execution mode
원문 언어: 영어
Orchestrate the complete implementation lifecycle from requirements to deployment
원문 언어: 영어
Create work plan from design document and obtain plan approval
원문 언어: 영어
Execute materialized fullstack task files with layer-aware agent routing
원문 언어: 영어
Orchestrate full-cycle implementation across backend and frontend layers
원문 언어: 영어
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
원문 언어: 영어
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions…
원문 언어: 영어
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
원문 언어: 영어
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.
원문 언어: 영어
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
원문 언어: 영어
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
원문 언어: 영어
Adjust an already-implemented UI in-session with verification against the design source
원문 언어: 영어
Selects the smallest set of task-execution skills and metacognitive safeguards for standalone task and diagnosis workflows.
원문 언어: 영어
Add integration/E2E tests to existing codebase using Design Docs
원문 언어: 영어
Adjust an already-implemented UI in-session with verification against the design source
원문 언어: 영어