agf-writing-adr
Use when tech-lead is about to record an architecture decision (new tech stack member, deviation from baseline, deployment / observability / auth scheme choice). Provides ADR structure, version-audit appendix format, and "what NOT to ADR" guidance. Replaces ad-hoc copy from ADR-000.
Profile →npx skills add pcliangx/AppGenesisForge --skill agf-writing-adr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Writing an ADR (Architecture Decision Record) Use this skill when: - A new technology / framework / vendor is being added to the stack (not already covered by ADR-000) - An existing baseline is being **deviated from** (e.g. swapping Postgres → SQLite for a specific service) - A cross-cutting decision needs explicit record (auth scheme, deployment shape, observability stack, LLM caching policy) -
What does the agf-writing-adr skill do?
Use when tech-lead is about to record an architecture decision (new tech stack member, deviation from baseline, deployment / observability / auth scheme choice). Provides ADR structure, version-audit appendix format, and "what NOT to ADR" guidance. Replaces ad-hoc copy from ADR-000.
How do I install it?
Run `npx skills add pcliangx/AppGenesisForge --skill agf-writing-adr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From pcliangx/AppGenesisForge, a repository with 359 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.