architect-specify
From the author
Use when you want guided trade-off analysis, multi-option comparison, or structured architectural decision facilitation before documenting. Optional for routine capture — team-boot writes lightweight ADR drafts directly.
Install
npx skills add tikalk/adlc-team-skills --skill architect-specify -a claude-code
Installs to .claude/skills/architect-specify/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Contains hidden text (invisible characters, long comments or encoded blobs)Medium
Why 76
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- product-specifytikalk/adlc-team-skillsUse when you want guided trade-off analysis, multi-option comparison, or structured product decision facilitation before documenting. Optional for routine capture — team-boot writes lightweight PDR drafts directly.Planning★ 143
- evals-specifytikalk/adlc-team-skillsUse when you want guided bottom-up error analysis, structured failure taxonomy discovery, or comprehensive trace coding before documenting eval criteria. Optional for routine capture — team-boot writes lightweight eval drafts directly.Planning★ 143
- architect-boottikalk/adlc-team-skillsUse when architecture work starts or a tech-stack or pattern decision emerges — injects the project ADR index (docs/adlc/memory/adr/, legacy .adlc/memory/adr/ fallback) as session context and pairs the decision with capture via /architect-specify; invoked from team-boot's Class Boots catalog.Planning★ 143
- architect-clarifytikalk/adlc-team-skillsUse when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.Planning★ 143
- oma-architecturefirst-fluke/oh-my-agentEvaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.Planning★ 1.4K
- architecture-designerJeffallan/claude-skillsUse when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.Planning★ 12.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in