Skills technical-decision-record

📦

technical-decision-record

Name: technical-decision-record
Author: ChaiWithJai

Content revision r1 Safe ⚙️ External commands

Document Technical Decisions Clearly

Teams lose context when technical choices are made without a durable record. This skill creates clear ADRs that capture options, rationale, consequences, and reversal cost.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "technical-decision-record" from https://skillstore.io/skills/chaiwithjai-technical-decision-record.md and its manifest at https://skillstore.io/api/skills/chaiwithjai-technical-decision-record/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/chaiwithjai-technical-decision-record.md Signed manifest GET /api/skills/chaiwithjai-technical-decision-record/manifest Signed lockfile GET /api/skills/chaiwithjai-technical-decision-record/lockfile

Test it

Using "technical-decision-record". We need to choose PostgreSQL, DynamoDB, or MongoDB for user profile data.

Expected outcome:

A completed ADR with context, constraints, three options, the selected database, consequences, risks, and reversal cost.

Using "technical-decision-record". Our team is moving from synchronous service calls to event-driven integration.

Expected outcome:

A decision record that explains the trigger, compares integration patterns, and documents operational risks for observability and retries.

Using "technical-decision-record". Review this draft ADR about adopting a third-party search service.

Expected outcome:

A review summary that flags missing cost limits, data residency concerns, rollback planning, and required stakeholder approvals.

Security Audit

Safe

v9 • 7/6/2026 Open versioned report

The only static finding is a false positive: SKILL.md line 76 is a fenced Markdown template, not shell execution. No evidence found for prompt injection, data exfiltration intent, or business logic abuse in the reviewed skill content.

Files scanned

189

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:76-133

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/chaiwithjai-technical-decision-record/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chaiwithjai-technical-decision-record/security.svg)](https://skillstore.io/skills/chaiwithjai-technical-decision-record?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chaiwithjai-technical-decision-record?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chaiwithjai-technical-decision-record/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chaiwithjai-technical-decision-record.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

ChaiWithJai. (2026). technical-decision-record security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chaiwithjai-technical-decision-record/audits/9

BibTeX citation

@techreport{chaiwithjai-chaiwithjai-technical-decision-record-2026,
  author = {ChaiWithJai},
  title = {technical-decision-record security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/chaiwithjai-technical-decision-record/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "technical-decision-record security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "ChaiWithJai"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/chaiwithjai-technical-decision-record/audits/9"
identifiers:
  - type: other
    value: "skillstore:chaiwithjai-technical-decision-record:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Choose a Database

Compare candidate databases and document the final selection with constraints, trade-offs, risks, and migration impact.

Record an Architecture Change

Capture why a service boundary, integration pattern, or infrastructure approach changed, including consequences for future teams.

Align Stakeholders

Prepare a clear decision record that helps product, security, and engineering teams review the same trade-offs.

Try These Prompts

Create a Basic ADR

Help me create an ADR for [decision]. Ask me for missing context before drafting the record.

Turn Notes into an ADR

Turn these notes into an ADR: [notes]. Include context, constraints, options, decision, consequences, risks, and reversibility.

Compare Technical Options

Compare these options for [decision]: [options]. Build an ADR that highlights trade-offs, stakeholder impact, and reversal cost.

Review an Existing ADR

Review this ADR for gaps: [ADR text]. Identify missing constraints, weak reasoning, unaddressed risks, and stakeholder questions.

Best Practices

Provide real constraints before asking for a final recommendation.
List at least two viable options, including the current approach when relevant.
Treat accepted ADRs as history and supersede them instead of rewriting them.

Avoid

Do not ask for an ADR after the team already ignored all alternatives.
Do not hide affected stakeholders from the decision record.
Do not spend heavy review time on decisions that are easy to reverse.

Frequently Asked Questions

Does this skill create Architecture Decision Records?

Yes. It guides the user through context, constraints, options, decision, consequences, risks, and reversibility.

Can it choose the best technology by itself?

No. It helps compare options, but it needs accurate constraints and team context from the user.

Can it review an existing ADR?

Yes. It can identify missing context, weak reasoning, unaddressed risks, and unclear stakeholder involvement.

Does it run commands or inspect project files?

No. The skill is prompt-only and provides a documentation framework.

What decisions fit this skill best?

It fits technology choices, architecture changes, service selection, process changes, and decisions with long-term trade-offs.

How should old ADRs be updated?

Old ADRs should remain unchanged. Create a new ADR that supersedes the earlier record and explains the change.

Developer Details

Author

ChaiWithJai

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/ChaiWithJai/claude-code-mastery/tree/main/exercises/05-domain-expertise/solution

Ref

dd4a3ef9f20ddf38830950b4bb713df96b431fd6

Maintenance freshness

7/18/2026

Usage

6 downloads · 250 views

File structure

📄 SKILL.md