Stats
Actions
Tags
From personal-os
SOP to design a technical solution and produce an Architecture Decision Document (ADD) — context review, options analysis (2-3 approaches with trade-offs), per-layer deep-dive (DB / backend / frontend / infra / SEO), risks, and decision. Use when a worker is delegated a dev architecture task, or asked to "design a solution", "produce an ADD", "evaluate technical options", "decide the architecture". SDLC Phase 2. Best run by the lead tier.
How this skill is triggered — by the user, by Claude, or both
Slash command
/personal-os:sop-dev-architectureThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
SOP: design a solution and produce an ADD. One decision per ADD.
SOP: design a solution and produce an ADD. One decision per ADD.
Follow procedure.md exactly.
Read the target repo's PROJECT_CONTEXT.md first — apply knowledge through the lens of the actual stack, never from assumptions. Reference: decision-rules.md.
Output: an ADD in the target repo (e.g. <repo>/docs/). Single-worker leaf SOP — does not fan out. Best run by the lead worker tier (high complexity).
npx claudepluginhub ygavrilov/plugin-personal-os --plugin personal-osGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.