New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Architect Clarify

by tikalk in tikalk/adlc-team-skills

A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

MITAuto-check passedDevelopment

Install Architect Clarify

skills CLI
$ npx skills add tikalk/adlc-team-skills --skill architect-clarify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tikalk/adlc-team-skills architect-clarify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architect/architect-clarify .claude/skills/architect-clarify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architect-clarify
GitHub stars
141
Token cost
~4.7k tokens
SKILL.md length
1,553 words
Files
8 (incl. scripts)
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

  • Works in 9 steps: Context Loading → Detect Lightweight Draft Format → ADR Analysis → …
  • ADRs need review
  • SKILL.md covers What this skill does, When to use, Process and Next Steps, plus 1 more section
  • Runs Shell and PowerShell scripts from its folder

What it does

Architect Clarify is an agent skill from tikalk/adlc-team-skills. Use when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts (for example `scripts/bash/ascii-generator.sh`, `scripts/bash/common.sh` and `scripts/bash/mermaid-generator.sh`).

It sits in Development, covering Architecture decision records. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.

When your agent uses it

  • ADRs need review
  • Gaps need filling
  • ADR status must be approved as Accepted before architecture generation

Example prompts

  • “/architect-clarify”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Context Loading
  2. Detect Lightweight Draft Format
  3. ADR Analysis
  4. 5: Risks & Gaps Analysis (Cross-Cutting)
  5. 6: Constitution Cross-Reference
  6. Gap Identification
  7. Interactive Refinement
  8. ADR Updates
  9. 5: ADR Approval ⭐

What it can do on your machine

Read from SKILL.md and the folder at commit 2dbed36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 7 files in scripts/ (Shell and PowerShell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architect Clarify loads about 4.7k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 1,553 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from tikalk/adlc-team-skills at commit 2dbed36, republished under its MIT licence (© tikalk). 1,553 words, ~4,734 tokens.

Download SKILL.mdSave it as .claude/skills/architect-clarify/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
architect-clarify
description
Use when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.
disable-model-invocation
true

architect-clarify

What this skill does

Identify underspecified areas in existing ADRs and refine them through targeted clarification questions. Ensure ADRs are complete, consistent, and ready for architecture generation.

You act as an Architecture Reviewer ensuring ADR quality by:

  • Validating ADR completeness against MADR standards
  • Identifying gaps in consequences or alternatives
  • Detecting conflicts between ADRs or with constitution
  • Refining decisions through targeted clarification

When to use

Use this skill:

  • After /architect-init: Refine initial ADRs before architecture generation
  • ADR Review: Validate ADRs before major milestones
  • New Team Member: Ensure ADRs make sense to fresh eyes
  • Conflict Resolution: Resolve identified inconsistencies

Do not use this skill when:

  • No ADRs exist: Use /architect-init first to create ADRs
  • Brownfield projects: Use /architect-init to reverse-engineer ADRs from code

Process

User Input
text
$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Examples of User Input:

  • "Focus on data architecture decisions - we're reconsidering database choice"
  • "Security ADRs need more detail for compliance review"
  • "ADR-003 consequences seem incomplete"
  • Empty input: Review all ADRs for completeness
Goal

Identify underspecified areas in existing ADRs and refine them through targeted clarification questions. Ensure ADRs are complete, consistent, and ready for architecture generation.

ADR Quality Checklist

Each ADR should have:

  • Clear context explaining the problem/opportunity
  • Explicit decision statement
  • Positive AND negative consequences
  • Common Alternatives documented (neutral trade-offs, not "Rejected because")
  • Risks identified with mitigation strategies
  • Status is accurate (Proposed/Accepted/Deprecated/Superseded/Discovered)
  • No conflicts with other ADRs
  • Alignment with constitution principles
  • No fabricated rejection rationale for reverse-engineered ADRs
Outline
  1. Load Current State: Parse ADRs from {REPO_ROOT}/.adlc/drafts/adr/ (individual file format) and {REPO_ROOT}/docs/adlc/memory/constitution.md (legacy {REPO_ROOT}/.adlc/memory/constitution.md fallback — ADR-401 dual-read)

IMPORTANT - Path Resolution:

  • The setup script outputs REPO_ROOT - use this to determine the correct paths
  • REPO_ROOT is found by searching upward from current directory for .adlc directory
  • NEVER use relative paths like .adlc/drafts/adr.md - always use {REPO_ROOT}/.adlc/drafts/adr/ADR-{NNN}.md
  • The setup script reads individual ADR files from the adr/ directory
  • When running from a subdirectory (e.g., a subproject directory), .adlc may be in the parent directory
  1. Analyze ADRs: Check each ADR against quality checklist
  2. Identify Gaps: List areas needing clarification
  3. Interactive Refinement: Ask targeted questions to fill gaps
  4. Update ADRs: Write refined ADRs back to file
Execution Steps
Phase 1: Context Loading

Objective: Establish current ADR state

  1. Run Prerequisites Script:

    • Execute scripts/bash/setup-architect.sh from repo root
    • Parse JSON for paths to memory files
    • Handle errors gracefully if files don't exist

  2. Load ADR File:

    • Read {REPO_ROOT}/.adlc/drafts/adr/adr.md for the ADR list
    • Read individual ADRs from {REPO_ROOT}/.adlc/drafts/adr/ADR-{NNN}.md
    • Count total ADRs and identify status distribution

  3. Load Constitution:

    • Read {REPO_ROOT}/docs/adlc/memory/constitution.md (legacy {REPO_ROOT}/.adlc/memory/constitution.md fallback) if either exists
    • Extract principles for alignment checking
    • Note governance constraints

  4. User Focus:

    • If user specified specific ADRs or areas, narrow scope
    • Otherwise, review all ADRs
Step 0: Detect Lightweight Draft Format

Check if the draft being reviewed uses the lightweight draft template (indicated by presence of type, evidence, source, revisit-when fields in frontmatter and ## Rejected Alternatives / ## Reason body sections without the full formal template sections).

If lightweight:

  1. Read the draft's captured fields (Context, Decision, Rejected Alternatives, Reason)
  2. Transform to full formal template:
    • ADR: full MADR format with Decision Drivers, Considered Options, Pros/Cons, Constitution Alignment, Related ADRs
    • PDR: full PDR format with Market Forces, Consequences, Alternatives Considered, Links
    • ChDR: full ChDR format with Issue Links, Commits, Consequences, Evidence
    • CDR: full CDR format with Context Type, Target Module, Descriptor, Evidence
    • EVAL: full eval format with Error Analysis, Pass/Fail Examples, Implementation Notes
  3. Enrich from session context (add details the lightweight draft may have omitted)
  4. Present the enriched draft for review

If already full format, proceed with normal review.

Phase 2: ADR Analysis

Objective: Identify quality gaps in each ADR

Quality Dimensions to Check

  1. Context Completeness:

    • Is the problem clearly stated?
    • Are the forces/drivers documented?
    • Is the decision scope clear?

  2. Decision Clarity:

    • Is the decision actionable?
    • Are implementation implications clear?
    • Can this decision be validated/tested?

  3. Consequence Coverage:

    • Are positive outcomes documented?
    • Are negative trade-offs acknowledged?
    • Are risks identified with mitigations?

  4. Alternatives Documentation:

    • Are at least 2 alternatives listed?
    • Is rejection reasoning clear for each?
    • Were reasonable options considered?

  5. Cross-ADR Consistency:

    • Do decisions conflict with other ADRs?
    • Are dependencies between ADRs documented?
    • Is terminology consistent?

  6. Constitution Alignment:

    • Does decision comply with MUST principles?
    • Are SHOULD principles addressed?
    • Are violations explicitly justified?
Phase 2.5: Risks & Gaps Analysis (Cross-Cutting)

Objective: Identify operational gaps, technical debt, SPOFs, and security concerns NOT documented across all views

Analysis Dimensions:

DimensionViews to CheckWhat to Look For
Operational GapsOperational (3.7), Deployment (3.6)Missing monitoring, undefined on-call, no runbooks, unclear rollback
Technical DebtDevelopment (3.5), Information (3.3)Deprecated dependencies, no tests, legacy code, schema debt
Single Points of FailureDeployment (3.6), Concurrency (3.4)Single DB instance, no redundancy, critical path bottlenecks
Security ConcernsAll viewsUnencrypted data, no auth, exposed secrets, missing audit trails

Gap Identification Process:

  1. Scan Each View: Check if view exists, identify missing critical sections, flag [TODO]/[TBD] areas
  2. Cross-View Analysis: Find inconsistencies (e.g., "high availability" stated but single instance shown)
  3. Risk Severity: CRITICAL (outage/breach/loss), HIGH (operational burden), MEDIUM (debt), LOW (documentation)

Gap ID Format: Section-based (e.g., 3.6.1 = Deployment View, gap #1)

Phase 2.6: Constitution Cross-Reference

Objective: Check ADRs against constitution for duplication and compliance

Analysis:

  1. Duplication Check: Does ADR restate a constitutional principle? Is decision already mandated?
  2. Compliance Check: Does decision violate MUST principles? Ignore SHOULD without justification?
  3. Override Classification: Is this an intentional deviation? Justified sufficiently?

Constitution Cross-Reference Table:

Issue TypeADRConstitution PrincipleAction Required
DuplicateADR-002§DataStorage mandates PostgreSQLRemove or convert to reference
ViolationADR-003§Security requires JWTAdd override justification or change
UnclearADR-004Silent on cachingClarify relationship
Show full SKILL.md (614 more words)Show less
Phase 3: Gap Identification

Objective: Prioritize clarification needs

Generate a gap report:

markdown
## ADR Clarification Report

### Summary
- Total ADRs: [N]
- Complete: [N]
- Needs Clarification: [N]

### Gaps by ADR

| ADR | Title | Gap Type | Severity | Priority |
|-----|-------|----------|----------|----------|
| ADR-001 | [Title] | Missing alternatives | HIGH | 1 |
| ADR-002 | [Title] | Incomplete consequences | MEDIUM | 2 |

### Cross-ADR Issues

| Issue | ADRs Affected | Description |
|-------|---------------|-------------|
| [Conflict] | ADR-001, ADR-003 | [Description of conflict] |
Gap Prioritization
  • CRITICAL: Constitution violations, missing decision statement
  • HIGH: No alternatives documented, missing consequences
  • MEDIUM: Incomplete risks, unclear context
  • LOW: Minor phrasing improvements, optional details
Phase 4: Interactive Refinement

Objective: Fill gaps through targeted questions

Question Format

For each gap requiring clarification:

markdown
## Clarification [N]: [ADR-XXX] - [Gap Type]

**Current State**: 
[Quote current ADR content]

**Gap Identified**: 
[Explain what's missing or unclear]

**Question**:
[Specific question to address the gap]

**Suggested Options** (if applicable):

| Option | Description |
|--------|-------------|
| A | [Option A] |
| B | [Option B] |
| C | [Custom response] |

Reply with your choice or provide additional context.
Constitution Cross-Reference Questions

When constitution issues are detected:

For Duplicates:

markdown
## Clarification [N]: Constitution Duplication Detected

**Question**: How should this duplicate ADR be handled?

**ADR**: ADR-XXX - [Title]
**Constitution Principle**: §[Section] - [Principle Name]
**Issue**: This ADR documents a decision already mandated by constitution

**Options**:
| Option | Action | Result |
|--------|--------|--------|
| A | Remove ADR | Decision covered by constitution only |
| B | Convert to Reference | Keep ADR as "See Constitution §X" |
| C | Add Context | Keep ADR with "Aligns with Constitution §X" |
| D | Extend | Keep ADR as "Extends Constitution §X" |

Reply with your choice (A/B/C/D).

For Violations (Option A PRIMARY - Amend Constitution):

markdown
## Clarification [N]: Constitution Violation Detected ⭐

**Question**: How should this constitutional violation be resolved?

**ADR**: ADR-XXX - [Title]
**Decision**: [What the ADR decides]
**Constitution Principle**: §[Section] - [Principle]
**Conflict**: [How they conflict]

**The constitution should evolve with the project's needs.**

**⭐ RECOMMENDED: A. Amend Constitution**
Update constitution §[Section] to accommodate this decision. This establishes a new principle for future decisions.

**Alternative Options**:
B. Override in ADR - Document justification for deviation
C. Revise ADR - Change decision to comply with constitution
D. Remove ADR - Delete and follow existing constitution

**Consider Amendment If**:
- [ ] This decision will be used again in the future
- [ ] Team's approach has evolved since constitution was written
- [ ] Existing principle is too restrictive for current needs

**Amendment Text**: [If choosing A, provide the specific constitutional amendment]

Reply with: "A [amendment text]" or "B/C/D [reasoning]"
Clarification Rules
  • Present one clarification at a time
  • Prioritize by severity - address CRITICAL/HIGH gaps first
  • For constitution violations, Option A (Amend) is PRIMARY
  • Limit to 5 clarifications per session (increased to 10 if architecture present)
  • Allow user to skip non-critical clarifications
  • Summarize changes after each answer
  • User can say "done" to end clarification early
Phase 5: ADR Updates

Objective: Write refined ADRs back to file

  1. Apply Clarifications:

    • Update ADR sections with new content
    • Preserve structure and formatting
    • Update "Last Updated" timestamps

  2. Resolve Conflicts:

    • If cross-ADR conflicts were found, propose resolution
    • Document decision to favor one ADR over another
    • Add cross-references between related ADRs

  3. Update Index:

    • Refresh ADR index table if titles changed
    • Update status if applicable

  4. Write File:

    • Atomic write to individual {REPO_ROOT}/.adlc/drafts/adr/ADR-{NNN}.md files
    • Preserve any ADRs that weren't modified
    • The setup script auto-regenerates adr.md and adr.md index after updates
Phase 5.5: ADR Approval ⭐

Objective: Get user confirmation to approve ADRs before architecture generation

This step is critical because implement only processes ADRs with "Accepted" status. ADRs with "Discovered" or "Proposed" status will be skipped.

Approval Request
markdown
## ADR Approval ⭐

**Total ADRs**: [N]
**Status Distribution**:
- Accepted: [N]
- Proposed: [N]
- Discovered: [N]

**⚠️ Important**: Only "Accepted" ADRs will be processed by `/architect-implement`

### Options

| Option | Action |
|--------|--------|
| A | Accept All - Change Proposed/Discovered → Accepted |
| B | Review Specific - Select individual ADRs to accept |
| C | Defer - Keep current status, decide later |

**Note**: You can also run `/architect-clarify` again later to approve additional ADRs.

Reply with A, B, or C (or "done" to skip).
Bulk Approval (Option A)

If user chooses Option A:

markdown
## Confirm Bulk Approval

Change [N] ADRs from Proposed/Discovered → Accepted?

| ADR | Current Status | New Status |
|-----|----------------|-------------|
| ADR-001 | Proposed | Accepted |
| ADR-002 | Discovered | Accepted |

Reply with "yes" to confirm or "no" to cancel.
Selective Approval (Option B)

If user chooses Option B, present ADRs one-by-one:

markdown
## ADR Approval: ADR-XXX

**Title**: [Title]
**Current Status**: [Proposed/Discovered]
**Context**: [Brief summary]

**Options**:
| Option | Action |
|--------|--------|
| A | Accept - Change to "Accepted" |
| B | Keep - Keep current status |
| C | Skip - Move to next ADR |

Reply with A, B, or C for ADR-XXX.
Post-Approval

After approval (or if user chooses C to defer):

markdown
## ADRs Approved

**Status Changes Applied**:
- ADR-001: Proposed → Accepted
- ADR-002: Discovered → Accepted
- ADR-007: Kept as Proposed

**Ready for Implementation**:
- Accepted ADRs: [N]
- Pending Approval: [N]

Run `/architect-implement` to generate AD.md from accepted ADRs.
Post-Approval State Update

After approval, you MUST write the workflow state file. Create the directory if it doesn't exist, then write {REPO_ROOT}/.adlc/architect/state.json:

bash
mkdir -p {REPO_ROOT}/.adlc/architect

Write this JSON content to the file (replace [N] with the actual count of approved ADRs and the timestamp with the current time):

json
{
  "workflow": {
    "clarify_completed": true,
    "clarify_completed_at": "2024-01-20T10:30:00Z",
    "adrs_approved_count": [N],
    "implement_started": false,
    "implement_started_at": null
  }
}

IMPORTANT: This workflow state file is REQUIRED before /architect-implement will execute. The implement command checks this state during pre-flight validation. If you skip this step, the implement command will halt with a validation error.

Key Rules
Non-Destructive Refinement
  • Never delete existing ADRs without explicit user approval
  • Preserve original intent when updating wording
  • Add, don't replace consequences and alternatives
  • Mark changes with updated timestamps
Focused Clarification
  • Ask one question at a time
  • Make questions specific and answerable
  • Provide suggested options when possible
  • Respect user's time - limit to 5 clarifications
Constitution Authority
  • Constitution violations are always flagged
  • ADRs cannot override MUST principles without explicit justification
  • Suggest constitution updates if conflict is systemic
Quality Over Quantity
  • Focus on material gaps that affect implementation
  • Skip cosmetic improvements unless user requests
  • Defer minor issues if major gaps remain
Completion Report

After clarification ends (all gaps addressed or user signals "done"):

markdown
## ADR Clarification Complete

**Changes Made**:
- ADR-001: Updated consequences section
- ADR-002: Added Common Alternatives (neutral trade-offs)
- ADR-003: Resolved conflict with ADR-001
- Constitution: Amended §DataStorage to allow NoSQL for document flexibility

**Risks & Gaps Status**:
- Critical gaps identified: [N] → [N resolved]
- High priority gaps: [N] → [N resolved]
- Cross-view inconsistencies: [N] → [N resolved]
- Integration with AD sections: [N updates]

**Remaining Gaps** (deferred):
- 3.6.2: Minor operational documentation (LOW)

**Cross-ADR Consistency**: ✅ Verified

**Constitution Alignment**:
- Duplicates resolved: [N]
- Violations addressed: [N]
- Constitution amended: [N] (if applicable)
- References added: [N]

**Recommended Next Steps**:
1. Review updated ADRs in `{REPO_ROOT}/.adlc/drafts/adr/adr.md`
2. Run `/architect-implement` to generate AD.md
3. Or run `/architect-specify` to create new ADRs for additional decisions
Workflow Status

⚠️ Required: You MUST run /architect-clarify before /architect-implement to approve ADRs.

Status Workflow:

  • init → "Discovered" (brownfield)
  • specify → "Proposed" (greenfield)
  • clarify → ask to approve → "Accepted" ⭐
  • implement → only reads "Accepted", skips Discovered/Proposed

Note: Do NOT invent intermediate statuses like "Validated". ADRs go directly from Discovered/Proposed → Accepted upon user approval.

Context

$ARGUMENTS

Next Steps

After clarify completes, run /architect-implement to generate the Architecture Description (AD.md).

Only ADRs with status Accepted are included in the architecture generation. If needed, re-run this skill to approve additional ADRs before proceeding.

Verification

Concrete outputs of this skill:

  • ADR files updated at {REPO_ROOT}/.adlc/drafts/adr/ADR-{NNN}.md with clarified content
  • ADR index refreshed at {REPO_ROOT}/.adlc/drafts/adr/adr.md
  • Constitution updated if amendments were approved
  • Workflow state written to {REPO_ROOT}/.adlc/architect/state.json with clarify_completed: true
  • At least one ADR status changed to Accepted, or explicit deferral recorded
  • Cross-ADR conflicts resolved or documented
  • Gap report showing critical/high gaps addressed

© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts) in skills/architect/architect-clarify of tikalk/adlc-team-skills.

  • SKILL.md
  • scripts/bash/ascii-generator.sh
  • scripts/bash/common.sh
  • scripts/bash/mermaid-generator.sh
  • scripts/bash/setup-architect.sh
  • scripts/powershell/ASCII-Generator.ps1
  • scripts/powershell/Mermaid-Generator.ps1
  • scripts/powershell/setup-architect.ps1

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Architect Clarify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architect Clarify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architect Clarify this skilltikalk/adlc-team-skills141—~4.7kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3804 repos~2.4kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    380 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed

  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed

  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed

  • Learning Opportunities

    DrCatHicks/learning-opportunities

    Facilitates deliberate skill development during AI-assisted coding.

    2.5k GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo

  • Team Boot

    tikalk/adlc-team-skills

    A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…

    141 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Change Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…

    141 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Change Init

    tikalk/adlc-team-skills

    A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.

    141 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed

  • Change Publish

    tikalk/adlc-team-skills

    A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.

    141 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Evals Analyze

    tikalk/adlc-team-skills

    A skill your agent uses when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.

    141 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Evals Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when draft eval criteria need refining, clustering, and acceptance into the published goldset with an isolated holdout split (goldset.md + goldset.json).

    141 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Architect Clarify

What does Architect Clarify do?

A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation. Architect Clarify is an agent skill from tikalk/adlc-team-skills. Use when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

When should I use Architect Clarify?

Architect Clarify fits situations like: ADRs need review; gaps need filling; ADR status must be approved as Accepted before architecture generation.

How do I install Architect Clarify in Claude Code?

Run `npx skills add tikalk/adlc-team-skills --skill architect-clarify -a claude-code`. Or copy the skill folder (skills/architect/architect-clarify in tikalk/adlc-team-skills) into .claude/skills/architect-clarify in your project. Claude Code loads it when a task matches its description.

How do I install Architect Clarify in Codex?

Run `npx skills add tikalk/adlc-team-skills --skill architect-clarify -a codex`. Or copy the skill folder (skills/architect/architect-clarify in tikalk/adlc-team-skills) into .agents/skills/architect-clarify in your project. Codex loads it when a task matches its description.

Can I use Architect Clarify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill architect-clarify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architect-clarify, .gemini/skills/architect-clarify, .github/skills/architect-clarify and .opencode/skills/architect-clarify in your project.

What does Architect Clarify need to run?

Going by SKILL.md and its folder, Architect Clarify needs a shell and PowerShell for the scripts in its folder. Our summary lists: A Bash shell; PowerShell.

Does Architect Clarify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architect Clarify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Architect Clarify use?

Architect Clarify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architect Clarify use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architect Clarify?

Skills that share tags, products or a category with Architect Clarify: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architect Clarify?

tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.