← all publishers

AdamAkhlaq

@adamakhlaq source repo

Report this profile Claim this profile

• 9 skills
• 0 followers
• 15 hours ago last updated

1. ▌
   Adr · adamakhlaq bundle

   Write or improve an Architecture Decision Record (ADR). Use when capturing a significant architectural or technical decision, when the user mentions ADRs, decision records, "why did we choose X over Y", or wants to document a technical trade-off. For broader non-architectural decisions (product, process, org), use the kdd skill instead.
   0
   installs
2. ▌
   Kdd · adamakhlaq bundle

   Write or improve a Key Decision Document (KDD) — a record of a significant decision that is not purely architectural: product direction, process, tooling, vendor, or cross-team choices. Use when the user wants to capture a key decision, its rationale, the options weighed, and who signed off. For a purely architectural/technical decision, use the adr skill instead.
   0
   installs
3. ▌
   Prd · adamakhlaq bundle

   Write or improve a Product Requirements Document (PRD) — the what and why of a product or feature: problem, users, goals, success metrics, requirements, and scope. Use when the user wants a PRD, product spec, feature brief, or product one-pager. For the technical "how", write an rfc; for recording a decision, a kdd or adr.
   0
   installs
4. ▌
   Rca · adamakhlaq bundle

   Write or improve a Root Cause Analysis / postmortem after an incident or outage. Use when the user mentions a postmortem, RCA, incident writeup, Correction of Errors (COE), "5 whys", blameless retro, or wants to document what broke and how to prevent recurrence.
   0
   installs
5. ▌
   Rfc · adamakhlaq bundle

   Write or improve an RFC / design document for a non-trivial change before building it. Use when the user wants a design doc, technical proposal, RFC, or to think through and socialise an approach with goals, alternatives, and trade-offs. For recording a decision that has already been made, use the adr skill; for incident analysis, use the rca skill.
   0
   installs
6. ▌
   Readme · adamakhlaq bundle

   Write or improve a project README. Use when the user wants to create, rewrite, or review a README — the front-door doc explaining what a project is, why it exists, and how to install and use it. Follows the Standard Readme spec.
   0
   installs
7. ▌
   Runbook · adamakhlaq bundle

   Write or improve an operational runbook / playbook for a service — how to operate it, what its alerts mean, and how to troubleshoot and recover it. Use when the user wants a runbook, on-call playbook, operational guide, or step-by-step recovery procedures. Pairs with the rca skill (a runbook is the proactive twin of a postmortem).
   0
   installs
8. ▌
   Object Object · adamakhlaq

   {{ONE OR TWO SENTENCES describing WHAT this skill does and — critically — WHEN Claude should reach for it. The description is the trigger: Claude reads it to decide whether to apply the skill, so make it sharp. Name the concrete situations, verbs, and phrases a user would use ("when the user asks to X", "when mentioning Y"). Say when NOT to use it and point to the better skill. A vague description means the skill fires at the wrong time or never fires.}}
   0
   installs
9. ▌
   Changelog · adamakhlaq bundle

   Create or update a CHANGELOG following the Keep a Changelog format and Semantic Versioning. Use when the user wants to write a changelog, add release notes, record what changed in a release, or maintain an [Unreleased] section.
   0
   installs