skills.rest
jvsandhu
jvsandhuCOMMUNITY
Explore all skills by this author →
GitHub

arch_decisions

Documents architecture decisions using ADR templates, database selection criteria, and capacity planning formulas.

Updated Jan 14, 2026
Search Tags:#documentation#scalability#adr#architecture decisions#capacity planning#database selection#sql vs nosql
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill arch-decisions-jvsandhu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch_decisions
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/arch_decisions
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill arch-decisions-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often make architecture decisions informally, losing the context and rationale behind choices like database selection or scaling strategy. This Skill provides a structured ADR (Architecture Decision Record) workflow so decisions are documented, reviewed, and traceable. ## Core Features & Use Cases - ADR Template: A ready-to-use Markdown template covering Status, Context, Decision, Consequences, and Alternatives. - Database Selection Guide: A comparison table for SQL vs NoSQL trade-offs (JOINs, ACID, throughput, horizontal scaling). - Capacity Planning: A simple formula to estimate RPS and peak load from DAU and per-user request counts. - Use Case: When choosing between PostgreSQL and MongoDB for a new service, draft an ADR with the template, score alternatives with the team, and commit the accepted record to the repository. ## Quick Start Draft an ADR for choosing PostgreSQL over MongoDB for our orders service, including context, consequences, and alternatives.

Frequently Asked Questions about arch_decisions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an architecture decision record (ADR)?▼

An ADR documents the status, context, decision, consequences, and alternatives of an architecture choice. Fill in the problem context, state the chosen solution, list positive and negative consequences, and record rejected alternatives with reasons.

How to choose between SQL and NoSQL databases?▼

Choose SQL when you need complex JOINs, ACID compliance, and transactions. Choose NoSQL when you need a flexible schema, high throughput, and horizontal scaling. Document the trade-offs in an ADR so the rationale stays visible.

How do I estimate capacity and RPS for a new service?▼

Multiply daily active users by requests per user per day, then divide by 86400 to get average RPS. Multiply by a peak factor (around 3) to estimate peak load, e.g. 1M DAU at 20 requests yields roughly 230 average and 700 peak RPS.

What are the phases of the ADR review workflow?▼

The workflow has three phases: problem identification (context, constraints, at least two alternatives), proposal (draft ADR, team RFC, scoring alternatives), and decision (consensus, documented consequences, committing the ADR file to the repository).

When should an ADR status change from Proposed to Accepted?▼

Change the status after the team has reviewed the proposal, alternatives have been scored against criteria, and consensus is reached. The long-term consequences must be written down honestly before committing the ADR to the repository.

Related Skills

Explore More Software Engineering Skills→
ricky-yoshricky-yosh

bf-create-spec

Interview stakeholders and generate a structured spec.txt draft for brownfield projects.

Community
Advanced
404kidwiz404kidwiz

terraform-engineer

Provision cloud infrastructure using Terraform/OpenTofu and HCL.

Community
Advanced
rnavarychrnavarych
14

role-database:capacity-planning

Estimate database storage growth and memory sizing for PostgreSQL, MySQL, MongoDB, and Redis.

Community
Advanced
ACGSpgpACGSpgp

architecture-decision-records

Create and manage Architecture Decision Records with lifecycle tracking.

Official
Intermediate