Skill

pith-arch

Structures architecture decisions with options table (pro/con/complexity), choice, risks, and next steps. For technology choices, design decisions, system design questions.

design

developer-tools

npx claudepluginhub abhisekjha/pith --plugin pith

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Architecture decision format. Structured. No narrative.

SKILL.md

Similar Skills

decision-support

104

Builds weighted decision matrices, analyzes trade-offs, and generates ADRs for architectural, technical, and process decisions like database selection or framework choice.

sdlc

architecture

10.9k

Creates or evaluates Architecture Decision Records (ADRs) for tech choices, design reviews, and new components, including options analysis, trade-offs, and consequences.

engineering

adr-architecture

Creates Architecture Decision Records (ADRs) capturing context, alternatives considered, trade-offs analyzed, and consequences for technology choices, infrastructure decisions, standards, and migrations.

4 files

thinking-frameworks-skills

Stats

Stars66

Forks5

Last CommitApr 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Option

Pro

Con

Complexity

...

low/med/high

...

low/med/high

...

low/med/high

Option

Pro

Con

Complexity

JWT

stateless, no DB reads

can't revoke, large cookie

low

Redis

revocable, small cookie

infra dependency

medium

DB session

simple, no new infra

DB read every request

low

Architecture decision format. Structured. No narrative.

Decision: [what is being decided — one line]

Option	Pro	Con	Complexity
A	...	...	low/med/high
B	...	...	low/med/high
C	...	...	low/med/high

Choice: [option name] — [single sentence reason]

Risks:

[risk]
[risk]

Next: [immediate first action]

Rules

Table rows: 2–5 options. If more, group similar ones.
Pro/Con: one phrase each. Not full sentences.
Choice: lead with option name. One sentence reason. No hedging.
Risks: 2–4 real blockers. Not generic "might take longer."
Next: one concrete action, not a plan.
If exploratory question (no decision needed): show table only, omit Choice/Risks/Next.

Example

Decision: session storage strategy for auth

Option	Pro	Con	Complexity
JWT	stateless, no DB reads	can't revoke, large cookie	low
Redis	revocable, small cookie	infra dependency	medium
DB session	simple, no new infra	DB read every request	low

Choice: Redis — revocability is required (security team req), team already operates Redis for cache

Risks:

Redis downtime = full auth outage (add fallback or circuit breaker)
Session data size can grow if not careful — set explicit TTLs

Next: Add ioredis to package.json, write src/lib/session.ts

One-shot. Does not persist.