Architect Verify Traceability — Design skill for Claude Code
Integration verification — confirm the issue → design → code → tests chain is intact, E2E + smoke suite pass, and the impact brief is complete before merge.
How to install Architect Verify Traceability
Installs to ~/.claude/skills/pappar-hitl-claude-plugin-architect-verify-traceability/SKILL.md
mkdir -p ~/.claude/skills/pappar-hitl-claude-plugin-architect-verify-traceability && curl -fsSL https://raw.githubusercontent.com/pappar/hitl-claude-plugin/HEAD/commands/architect-verify-traceability.md -o ~/.claude/skills/pappar-hitl-claude-plugin-architect-verify-traceability/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Architect Verify Traceability does
description: Integration verification — confirm the issue → design → code → tests chain is intact, E2E + smoke suite pass, and the impact brief is complete before merge argument-hint: "[PR link or issue number]"
Use the `spec-conformance-reviewer` agent to verify traceability for $ARGUMENTS.
Confirm the chain is unbroken: GitHub issue exists → design PR merged → implementation matches LLD → tests cover the spec → impact brief reviewed → rollout plan approved.
Then verify the following
Alternatives in Design
- Od Contribute — Open a first-contribution PR (or bug issue) on nexu-io/open-design — works for non-coders too 91.8k ★
- Icm Architect — Claude skill: design any process, idea, or problem into an ICM workspace (folder structure as agent architectu 1.3k ★
- Deepen — Spare-budget design pass 1.1k ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Check Traceability
Verify links from use cases and requirements to design, code, tests, and releases
Qb
Behavior validation - verify tests pass and outputs match design.
Architect Review Design
Review HLD, LLD, and ADR for a feature — verify design is implementable and manifest-consistent before approvi
Interaction
Define interaction rules — modal vs bottom sheet, expand vs navigate, optimistic UI, undo vs confirm
Final Validation
Use before a push, merge, release, or completion claim for any feature, refactor, UI, documentation, or depend
Change
설계가 순수 함수와 UI 책임을 먼저 고정하고, unit → ui → integration → e2e 각 계층에서 red 확인 뒤 구현하고 green을 확인한다. Git 작업은 자동으로 붙지 않는다
Related Agents
Exec E2e Scribe
The fix-issue writer of the stage-4 round — turns ONE real e2e failure into a complete issue in the house plan
Mr Test Impact
Use to map a merge request / pull request's changes (GitLab, GitHub, Azure DevOps, Bitbucket) to the existing
Sf Org Verifier
Verifies a Salesforce change in the live org after deployment - smoke probes, data and limit queries, log capt