Document decision rationale into standardized Markdown decision records.
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill explain-hereinthehive
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
Document decision rationale and project context into reusable decision records.
Create a new decision record for the recently implemented authentication module.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
rjschieAutomate Architecture Decision Record creation, indexing, and repository updates.
FaysilAlshareefCreate numbered MADR files with context, decision, and consequences sections.
baasith6Document technical decisions using structured Architecture Decision Records with sequential numbering.
bradtaylorsfGenerate Architecture Decision Records with a standardized template.
