From harness-claude
Make and record an architecture/design decision for non-trivial work — new subsystems, interfaces, data models, or significant refactors. Use when /plan flags a load-bearing decision. Delegates to the harness-claude:architect agent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness-claude:architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: a concise, reviewable design with explicit trade-offs — not analysis paralysis.
Goal: a concise, reviewable design with explicit trade-offs — not analysis paralysis.
Only when the design is non-obvious: a new subsystem, a public interface/data model, a cross-cutting change, or a refactor with several viable shapes. Skip for routine work.
harness-claude:architect agent with the problem, constraints, and the
existing architecture it must fit.## Context
## Decision
## Alternatives & why not
## Consequences / trade-offs
## Interfaces & data model
## Risks & mitigations
Save the ADR (session file, or docs/adr/ if the project keeps them).
A single recommended design with trade-offs stated. Then /harness-claude:implement.
npx claudepluginhub vasuag09/harness-claude --plugin harness-claudeProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.