engineering-docs 플러그인
22 engineering documentation skills covering the complete software lifecycle.
engineering-docs 플러그인 설치 방법
두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.
/plugin marketplace add fattain-naime/engineering-docs
/plugin install engineering-docs@engineering-docsengineering-docs 구성 요소
플러그인 파일에서 읽어온 28개의 항목입니다.
Agents 4
@agent-engineering-docs:name 으로 호출- @agent-engineering-docs:api-designersonnet
|
- @agent-engineering-docs:architecture-reviewersonnet
|
- @agent-engineering-docs:documentation-generatorsonnet
|
- @agent-engineering-docs:test-strategistsonnet
|
Skills 22
작업이 일치하면 Claude가 로드합니다- admin-access-control-specification
Specify admin roles, permissions, and every admin-facing control in a system - a full role-permission matrix (RBAC), the principle of least privilege applied concretely, admin action audit logging, and emergency/break-glass access procedures. Use whenever a system has more than one privilege level, before building the admin panel or access-control logic.
- api-design-document
Design a production-ready API specification aligned with OpenAPI 3.1 standards. Covers resource modeling, endpoint design, request/response contracts, authentication, versioning strategy, error handling, rate limiting, and pagination. Use when designing a new REST, GraphQL, or event-driven API.
- architecture-decision-record
Create a standalone Architecture Decision Record (ADR) for a single significant architectural decision. Captures context, decision, alternatives considered, and consequences. ADRs are immutable - once accepted, they are never edited, only superseded by a new ADR.
- business-concept
Turn a raw business idea into a complete business concept document. Covers problem, target users, value proposition, monetization, scope, timeline, and constraints. Use as the first step before any technical documentation.
- database-design-document
Design a production database schema including ERD, table definitions, data dictionary, indexing strategy, normalization decisions, and migration plan. Use when designing a new database, adding major entities, or documenting an existing schema.
- deployment-plan
Write a production deployment plan covering environment specs, deployment strategy (Blue-Green, Canary, Rolling, or Direct), step-by-step execution runsheet, go/no-go criteria, monitoring plan, and rollback procedure. Use before any non-trivial production release.
- design-system-specification
Design a production-ready Design System and UI/UX visual style guide. Covers design tokens (colors, typography, spacing, shadows, radius), components (buttons, inputs, cards, tables, modals, navigation), layouts, interaction/hover states, iconography, motion design, responsive behavior, accessibility (WCAG 2.2), and dark/light mode rules. Use when starting a new website/app design or standardizing existing branding.
- disaster-recovery-plan
Write a disaster recovery and business continuity plan defining RTO/RPO targets, backup and failover procedures, DR tiers, and a recovery drill cadence for surviving major infrastructure loss, data corruption, ransomware, or regional outages. Use before launch of any system holding critical or financial data, or to formalize continuity commitments for compliance (PCI-DSS, SOC 2, ISO 22301).
- implementation-plan
Create a phased implementation roadmap that sequences the technical build of an entire project - build order, module dependencies, environment/tooling setup, per-phase Definition of Ready/Done, and integration checkpoints. Use after the project plan and architecture exist, to turn "what we're building and when" into "in what technical order we actually build it."
- incident-postmortem
Write a blameless post-incident review (post-mortem / RCA) that documents what happened, the timeline, root cause analysis, impact assessment, and concrete action items to prevent recurrence. Follows Google SRE blameless post-mortem culture.
- project-plan
Create a project delivery plan covering scope, milestones, timeline, work breakdown, resourcing, stakeholder roles (RACI), dependencies, budget, quality gates, and a project-level risk register. Use at the start of any project to define who is building what, in what order, by when - before any code is written.
- security-threat-model
Produce a structured security threat model using the STRIDE framework, identify trust boundaries, enumerate attack vectors, assess risk, and define concrete mitigations. Use when reviewing security of a new feature, system, or integration.
- slo-error-budget-document
Define Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets for a service, including multi-window multi-burn-rate alerting and an error budget policy. Use when establishing reliability targets, negotiating an external SLA, or deciding how much risk a team can spend on shipping velocity versus reliability work.
- system-architecture-document
Create a System Architecture Document (SAD) with C4 model diagrams, 4+1 view decomposition, integration maps, NFR constraints, and an Architecture Decision Record log. Use when documenting how an entire system or major subsystem is structured.
- technical-blueprint
Write a Technical Design Document (TDD) / Software Design Document (SDD) that details how a specific feature or component will be built. Covers problem statement, proposed design, data model, API contracts, alternatives considered, security threat analysis, test plan, and rollback plan. Use when an engineer or team needs to align on the implementation approach before writing code.
- technical-feasibility-study
Assess whether a proposed technical solution is viable given the current stack, team, timeline, and constraints. Produces a go/no-go recommendation with evidence. Use before committing engineering resources to design or implementation.
- technical-runbook
Write a production operations runbook that provides on-call engineers with step-by-step procedures for operating, monitoring, and recovering a system. Covers system overview, alert response procedures, common failure modes, diagnostic commands, escalation paths, and maintenance procedures. Modeled on Google SRE runbook standards.
- technical-specification
Write a technical specification (SRS/TSD) that captures stakeholder needs, system requirements, functional behavior, non-functional constraints, and acceptance criteria. Use when starting any significant engineering initiative.
- test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
- user-personas-behavior
Define who a product is for, what they're trying to accomplish, how success is measured, and what to instrument to know if it's working. Covers user personas (goal- and behavior-based, not demographic), jobs-to-be-done, success metrics/KPIs, and an analytics/event-tracking plan. Use before or alongside requirements gathering so "who is this for and how do we know it's working" is answered explicitly.
- using-engineering-docs
The entry point for this plugin. Give it a raw project idea or concept and it takes over: runs a discovery conversation, decides which document skills apply and in what order, then generates that full document set one skill at a time. Use when you have an idea and don't yet know which documents you need.
- ux-flow-specification
Document the complete user experience of a product - information architecture, user journeys, screen-by-screen flows, and every UI state (loading, empty, error, success) - independent of visual styling. Use to define exactly how a user moves through a product before or alongside implementation, so navigation and edge-case behavior are decided upfront rather than improvised.
Hooks 1
다음 이벤트에서 실행됩니다- SessionStartcommand
startup|resume|clear|compact|fork
MCP server 1
플러그인과 함께 시작됩니다- engineering-docsstdio
node ${CLAUDE_PLUGIN_ROOT}/scripts/validate.js
Claude Code에서 engineering-docs 사용하기
이름으로 agent를 요청하세요:
@agent-engineering-docs:api-designer
@agent-engineering-docs:architecture-reviewerSkills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.
업데이트, 비활성화 또는 삭제
- 플러그인 업데이트 (shell)
- claude plugin update engineering-docs@engineering-docs
- marketplace 새로고침
- /plugin marketplace update engineering-docs
- 일시적으로 비활성화
- /plugin disable engineering-docs@engineering-docs
- 삭제
- /plugin uninstall engineering-docs@engineering-docs
engineering-docs의 스킬
- admin-access-control-specificationfattain-naime/engineering-docs
Specify admin roles, permissions, and every admin-facing control in a system - a full role-permission matrix (RBAC), the principle of least privilege applied concretely, admin action audit logging, and emergency/break-glass access procedures. Use whenever a system has more than one privilege level, before building the admin panel or access-control logic.
2개 파일6스타 - api-design-documentfattain-naime/engineering-docs
Design a production-ready API specification aligned with OpenAPI 3.1 standards. Covers resource modeling, endpoint design, request/response contracts, authentication, versioning strategy, error handling, rate limiting, and pagination. Use when designing a new REST, GraphQL, or event-driven API.
2개 파일6스타 - architecture-decision-recordfattain-naime/engineering-docs
Create a standalone Architecture Decision Record (ADR) for a single significant architectural decision. Captures context, decision, alternatives considered, and consequences. ADRs are immutable - once accepted, they are never edited, only superseded by a new ADR.
2개 파일6스타 - business-conceptfattain-naime/engineering-docs
Turn a raw business idea into a complete business concept document. Covers problem, target users, value proposition, monetization, scope, timeline, and constraints. Use as the first step before any technical documentation.
2개 파일6스타 - database-design-documentfattain-naime/engineering-docs
Design a production database schema including ERD, table definitions, data dictionary, indexing strategy, normalization decisions, and migration plan. Use when designing a new database, adding major entities, or documenting an existing schema.
2개 파일6스타 - deployment-planfattain-naime/engineering-docs
Write a production deployment plan covering environment specs, deployment strategy (Blue-Green, Canary, Rolling, or Direct), step-by-step execution runsheet, go/no-go criteria, monitoring plan, and rollback procedure. Use before any non-trivial production release.
2개 파일6스타 - design-system-specificationfattain-naime/engineering-docs
Design a production-ready Design System and UI/UX visual style guide. Covers design tokens (colors, typography, spacing, shadows, radius), components (buttons, inputs, cards, tables, modals, navigation), layouts, interaction/hover states, iconography, motion design, responsive behavior, accessibility (WCAG 2.2), and dark/light mode rules. Use when starting a new website/app design or standardizing existing branding.
2개 파일6스타 - disaster-recovery-planfattain-naime/engineering-docs
Write a disaster recovery and business continuity plan defining RTO/RPO targets, backup and failover procedures, DR tiers, and a recovery drill cadence for surviving major infrastructure loss, data corruption, ransomware, or regional outages. Use before launch of any system holding critical or financial data, or to formalize continuity commitments for compliance (PCI-DSS, SOC 2, ISO 22301).
2개 파일6스타 - implementation-planfattain-naime/engineering-docs
Create a phased implementation roadmap that sequences the technical build of an entire project - build order, module dependencies, environment/tooling setup, per-phase Definition of Ready/Done, and integration checkpoints. Use after the project plan and architecture exist, to turn "what we're building and when" into "in what technical order we actually build it."
2개 파일6스타 - incident-postmortemfattain-naime/engineering-docs
Write a blameless post-incident review (post-mortem / RCA) that documents what happened, the timeline, root cause analysis, impact assessment, and concrete action items to prevent recurrence. Follows Google SRE blameless post-mortem culture.
2개 파일6스타 - project-planfattain-naime/engineering-docs
Create a project delivery plan covering scope, milestones, timeline, work breakdown, resourcing, stakeholder roles (RACI), dependencies, budget, quality gates, and a project-level risk register. Use at the start of any project to define who is building what, in what order, by when - before any code is written.
2개 파일6스타 - security-threat-modelfattain-naime/engineering-docs
Produce a structured security threat model using the STRIDE framework, identify trust boundaries, enumerate attack vectors, assess risk, and define concrete mitigations. Use when reviewing security of a new feature, system, or integration.
2개 파일6스타 - slo-error-budget-documentfattain-naime/engineering-docs
Define Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets for a service, including multi-window multi-burn-rate alerting and an error budget policy. Use when establishing reliability targets, negotiating an external SLA, or deciding how much risk a team can spend on shipping velocity versus reliability work.
2개 파일6스타 - system-architecture-documentfattain-naime/engineering-docs
Create a System Architecture Document (SAD) with C4 model diagrams, 4+1 view decomposition, integration maps, NFR constraints, and an Architecture Decision Record log. Use when documenting how an entire system or major subsystem is structured.
3개 파일6스타 - technical-blueprintfattain-naime/engineering-docs
Write a Technical Design Document (TDD) / Software Design Document (SDD) that details how a specific feature or component will be built. Covers problem statement, proposed design, data model, API contracts, alternatives considered, security threat analysis, test plan, and rollback plan. Use when an engineer or team needs to align on the implementation approach before writing code.
2개 파일6스타 - technical-feasibility-studyfattain-naime/engineering-docs
Assess whether a proposed technical solution is viable given the current stack, team, timeline, and constraints. Produces a go/no-go recommendation with evidence. Use before committing engineering resources to design or implementation.
2개 파일6스타 - technical-runbookfattain-naime/engineering-docs
Write a production operations runbook that provides on-call engineers with step-by-step procedures for operating, monitoring, and recovering a system. Covers system overview, alert response procedures, common failure modes, diagnostic commands, escalation paths, and maintenance procedures. Modeled on Google SRE runbook standards.
2개 파일6스타 - technical-specificationfattain-naime/engineering-docs
Write a technical specification (SRS/TSD) that captures stakeholder needs, system requirements, functional behavior, non-functional constraints, and acceptance criteria. Use when starting any significant engineering initiative.
2개 파일6스타 - test-strategy-documentfattain-naime/engineering-docs
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
2개 파일6스타 - user-personas-behaviorfattain-naime/engineering-docs
Define who a product is for, what they're trying to accomplish, how success is measured, and what to instrument to know if it's working. Covers user personas (goal- and behavior-based, not demographic), jobs-to-be-done, success metrics/KPIs, and an analytics/event-tracking plan. Use before or alongside requirements gathering so "who is this for and how do we know it's working" is answered explicitly.
2개 파일6스타 - using-engineering-docsfattain-naime/engineering-docs
The entry point for this plugin. Give it a raw project idea or concept and it takes over: runs a discovery conversation, decides which document skills apply and in what order, then generates that full document set one skill at a time. Use when you have an idea and don't yet know which documents you need.
3개 파일6스타 - ux-flow-specificationfattain-naime/engineering-docs
Document the complete user experience of a product - information architecture, user journeys, screen-by-screen flows, and every UI state (loading, empty, error, success) - independent of visual styling. Use to define exactly how a user moves through a product before or alongside implementation, so navigation and edge-case behavior are decided upfront rather than improvised.
2개 파일6스타
engineering-docs 플러그인 질문
engineering-docs 플러그인은 어떻게 설치하나요?
Claude Code에서 /plugin marketplace add fattain-naime/engineering-docs를 실행한 다음 /plugin install engineering-docs@engineering-docs을 실행하십시오.
engineering-docs 플러그인에는 무엇이 포함되나요?
engineering-docs은(는) 4개 에이전트, 22개 스킬, 훅, MCP 서버을(를) 묶습니다.
engineering-docs에는 어떤 agent가 포함되어 있나요?
api-designer, architecture-reviewer, documentation-generator, test-strategist입니다. @agent-engineering-docs:api-designer로 호출하세요.
engineering-docs 플러그인을 어떻게 업데이트하거나 삭제하나요?
shell에서 claude plugin update engineering-docs@engineering-docs를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall engineering-docs@engineering-docs을 사용하세요.
engineering-docs 플러그인의 라이선스는 무엇인가요?
플러그인 manifest에 명시된 대로 MIT입니다.