skills.rest
hereinthehive
hereinthehiveCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

explain

Document decision rationale into standardized Markdown decision records.

5|Updated Jan 14, 2026
Search Tags:#architecture#documentation#onboarding#rationale#explain#decision-records#team-workflow
One-click install
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill explain-hereinthehive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/explain
Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill explain-hereinthehive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document decision rationale and project context into reusable decision records.

Core Features & Use Cases

  • Create standardized decision records that preserve architectural rationale for future developers.
  • Provide a centralized, searchable source of context for onboarding, audits, and maintenance.
  • Use Case: A new feature requires a documented rationale to justify design choices to stakeholders.

Quick Start

Create a new decision record for the recently implemented authentication module.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I document architectural decisions for software onboarding and audits?▼

Decision records document architectural rationale and project context into a standardized directory. They provide a centralized, searchable source for onboarding, audits, and long-term maintenance traceability.

What is the best way to capture project context in a standardized decisions directory?▼

The best way to capture project context is generating auto-numbered Markdown records with required frontmatter. This standardizes naming and descriptions inside a decisions directory for easy retrieval.

Can I use decision records to justify design choices to stakeholders for a new feature?▼

Yes, decision records justify design choices to stakeholders. Creating a documented rationale for new features ensures architectural context is preserved and traceable during stakeholder reviews.

Does this decision record tool work for software projects of any size?▼

Yes, documenting decision rationale works for software projects of any size. It applies wherever onboarding, audits, and long-term maintenance require preserved context and traceability.

What format are decision records generated in for team workflow documentation?▼

Decision records are generated as numbered, concise Markdown files. They require frontmatter containing a name and description to ensure standardized documentation across the team workflow.

Related Skills

Explore More Software Engineering Skills→
rjschierjschie

adr

Automate Architecture Decision Record creation, indexing, and repository updates.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

adr

Create numbered MADR files with context, decision, and consequences sections.

Community
Intermediate
baasith6baasith6

architecture-decision-records

Document technical decisions using structured Architecture Decision Records with sequential numbering.

Community
Intermediate
bradtaylorsfbradtaylorsf
8

architecture-decisions

Generate Architecture Decision Records with a standardized template.

Community
Basic