Skip to main content

document-a-software-architecture

Document a software system's boundaries, components, data, decisions, runtime, security, failure modes, and change paths. Use when maintainers or reviewers need a current architecture guide grounded in the real implementation.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
document-a-software-architecture
category
write
description
Document a software system's boundaries, components, data, decisions, runtime, security, failure modes, and change paths. Use when maintainers or reviewers need a current architecture guide grounded in the real implementation.
# document-a-software-architecture Explain the system at the level needed to change and operate it. Prefer a small set of linked views and decision records over one diagram that claims to show everything. ## Inputs - Gather repositories, deployment configuration, schemas, interfaces, infrastructure, observability, and ownership. - Review current runtime evidence, dependency inventories, incidents, threat models, and architecture decisions. - Define the audience and the maintenance or review questions the document must answer. ## Procedure 1. State system purpose, users, scope, non-goals, quality attributes, and important constraints. 2. Draw context and trust boundaries around people, external systems, and owned services. 3. Map major components, responsibilities, interfaces, dependencies, and owners. 4. Trace critical request, event, data, and control flows end to end. 5. Document persistent data, lifecycle, consistency, privacy, retention, and recovery. 6. Explain deployment units, environments, configuration, secrets, scaling, and network boundaries. 7. Record availability, security, capacity, observability, and operational assumptions. 8. Describe expected failures, containment, degradation, retry, reconciliation, and recovery behavior. 9. Link consequential decisions and known debt rather than rewriting their full history. 10. Verify diagrams and claims against code, deployed configuration, and responsible owners; add freshness triggers. ## Boundaries Do not publish secrets, private endpoints, customer data paths, or exploitable detail beyond the document's approved audience. Never document intended architecture as current without labeling the gap. ## Done - Context, components, interfaces, data, deployment, trust, and ownership views are linked - Critical flows and failure behavior are checked against implementation and runtime evidence - Constraints, decisions, debt, and intended changes are visibly distinguished - The document has an owner and review triggers tied to system change
GitHub에서 보기